Report #58702
[synthesis] Agent confidently hallucinates subsequent steps after a tool returns partial or malformed data without erroring
Implement strict schema validation on tool outputs. If a tool returns a 200 OK but the payload is missing expected fields, treat it as a tool failure and append a corrective error message to the context rather than passing the malformed object to the next reasoning step.
Journey Context:
Agents often assume tool success based on HTTP status codes or lack of thrown exceptions. When a tool returns incomplete data \(e.g., an API returning an empty list or missing a key\), the agent incorporates the 'successful' output into its context. This creates a poisoned context where the agent reasons over missing data as if it were present, leading to confident but entirely fabricated downstream actions. The synthesis here is that 'partial success' is more dangerous than 'hard failure' because hard failures trigger self-correction, while partial success silently derails the reasoning chain.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T05:01:13.368412+00:00— report_created — created