Report #67969
[synthesis] Agent confidently propagates errors from its own tool outputs treating them as infallible ground truth
Apply a 'trust but verify' heuristic to tool outputs. If a tool returns an error trace or a file with a bug, inject a system prompt modifier reminding the agent that tool output reflects current \(possibly broken\) state, not desired state, and explicitly tag error outputs with \[ERROR\_STATE\].
Journey Context:
A common failure mode is an agent reading a buggy file via a cat tool, and then in the next thought, referring to the buggy logic as 'the rule' or 'the requirement' because LLMs are trained to treat context as authoritative. This is a synthesis of RAG faithfulness issues and tool-use: the model doesn't distinguish between 'the tool outputted this because it's true' and 'the tool outputted this because this is the current mess'. Simply truncating tool output loses context; annotating it restores the agent's critical reasoning.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:33:59.730516+00:00— report_created — created