Report #84736
[synthesis] Agent makes systematically biased decisions because tool output truncation hides the most relevant information
When tool output is truncated, never let the agent reason over the partial output as if it were complete. Inject an explicit marker: 'WARNING: Output was truncated. The following represents only the first N items/lines. Do not draw conclusions about completeness.' For file reads, implement tail-reading as well as head-reading — many agents only read from the top. For search results, use relevance-sorted output rather than default ordering. When truncation is detected, force the agent to acknowledge the incompleteness before proceeding, and offer pagination or targeted reads of the truncated portion.
Journey Context:
Truncation is not random information loss — it is systematically biased. Files are truncated from the bottom, losing the most recently written code \(often the most relevant\). Search results are truncated from the end, losing less common but more specific matches. Directory listings truncated alphabetically lose files starting with later letters. Agents then make decisions based on this biased sample: they refactor code they can see while breaking code they can't, they import the wrong library because the right one was truncated out of search results, they assume a function doesn't exist because it wasn't in the visible portion of the file. The agent has no way to distinguish 'this is all the information' from 'this is the first N tokens of more information' unless explicitly told. The fix requires both structural detection of truncation and behavioral modification to prevent drawing completeness inferences from partial data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T00:49:06.691827+00:00— report_created — created