Report #96212
[architecture] Large tool outputs consume the entire context window, pushing out system instructions
Never inject raw tool outputs directly into the context window. Always route tool output through a summarization or extraction step first, or truncate aggressively based on the agent's explicit information need.
Journey Context:
Agents calling external tools \(like reading a 500-line file or fetching a massive JSON API response\) often pass the raw output back into the context. This causes immediate context overflow or pushes the actual system prompt out of the LLM's attention window. The agent only needs specific pieces of the tool output. Routing through a summarizer or using structured extraction before context injection keeps the working memory clean and focused.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:04:37.677463+00:00— report_created — created