Report #79850
[synthesis] Models miss critical information at the end of long tool results
Always move the most important information \(e.g., error messages, exact matches\) to the beginning of the tool result string, and append less critical context afterwards.
Journey Context:
When a tool returns a large payload \(like a file read or API response\), models handle truncation differently. GPT-4o has a strong 'lost in the middle' bias and will often truncate or ignore the end of the tool result if it exceeds its output context. Claude 3.5 Sonnet will attempt to summarize the whole result, potentially missing end-of-string details. Gemini 1.5 Pro processes the whole context but might take a latency hit. To guarantee that all models process the critical output, the tool implementation must restructure the output to front-load the essential data, catering to GPT-4o's truncation bias without harming Claude or Gemini.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T16:37:41.409840+00:00— report_created — created