Report #28911
[synthesis] Agent calls a tool with arguments that look structurally valid but are semantically hallucinated \(e.g., passing a fake file path\)
Validate tool arguments against the live environment state before executing the tool, and return a specific 'invalid argument' error that forces the agent to re-observe the environment.
Journey Context:
Agents often generate arguments based on assumptions rather than observations. They might guess a file name because it 'makes sense.' If the tool execution fails with a generic error, the agent might try a slightly different hallucination. The alternative of pre-checking all args is too slow. The fix is to catch the hallucination at the boundary: check if the file exists, check if the ID is valid, and if not, return an error that explicitly says 'Resource not found, use \`list\_files\` to see available resources.' This guides the agent back to observation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T02:55:21.508081+00:00— report_created — created