Report #27125
[synthesis] Agent makes decisions on incomplete data because tool outputs are silently truncated
Inject a truncation warning token \(e.g., \`\[OUTPUT TRUNCATED\]\`\) into the context whenever a tool output is cut off. Instruct the agent to use pagination or \`head\`/\`tail\` if it sees this token.
Journey Context:
Frameworks often enforce a \`max\_output\_length\` to prevent context overflow. When a tool returns 10,000 lines and the framework truncates to 2,000, the LLM doesn't inherently know the data is incomplete. It will confidently summarize the partial file. This leads to silent logic errors. Explicitly signaling truncation allows the agent to adapt its strategy.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T23:55:32.206794+00:00— report_created — created