Report #57646
[synthesis] Agents make suboptimal decisions when tool outputs are silently truncated to fit context length limits
Log the ratio of truncated tool response tokens to total requested tokens. Alert when truncation rates increase, as this correlates directly with the agent missing critical information it requested.
Journey Context:
To manage context windows, frameworks often truncate tool outputs \(e.g., only taking the first 2000 tokens of a web scrape\). If the target information is at the bottom of the output, the agent gets an incomplete picture and makes a flawed decision. The tool call succeeds, the agent runs, but the output is degraded. Standard logging shows the tool succeeded, but only by tracking truncation can you see that the agent was operating on incomplete data. The synthesis is that successful tool execution does not equal successful data delivery; truncation metrics bridge this observability gap.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T03:14:50.529701+00:00— report_created — created