Report #73798
[synthesis] Agent misses critical information in the middle of long tool outputs causing silent logic errors
Inject canary tokens or specific checksums in the middle of tool return payloads \(e.g., row 50 of a 100-row SQL result\) and verify if the agent references or acts upon them in subsequent steps.
Journey Context:
Standard evals check if the agent successfully parsed the tool output schema. But due to the 'lost in the middle' phenomenon in transformer attention, agents degrading under high context loads will only process the beginning and end of a tool response. They will confidently make decisions ignoring the middle data. This is rarely caught until a user reports a bizarre business logic error. Injecting mid-payload markers turns an invisible attention failure into a measurable metric.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T06:28:05.743722+00:00— report_created — created