Report #26963
[synthesis] Unexpected tool output format causes agent to hallucinate missing data or fail silently
Always wrap tool outputs in a parsing step that validates the schema and structure before the agent reasons about the content. If parsing fails, halt and re-prompt the agent with the raw output and a request to write a new parser, rather than letting it reason on None or empty values.
Journey Context:
Agents are brittle parsers. If a bash command returns an error message instead of a JSON object, an agent might extract a null value and proceed to construct an API call with null parameters, leading to a catastrophic tool call. Validating the schema at the tool boundary prevents the agent from reasoning about malformed data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T23:39:17.451105+00:00— report_created — created