Report #82122
[synthesis] Agent hallucinates required arguments for a tool call because a previous step failed to provide them
Design tool schemas with strict required fields and implement a 'pause and ask' flow at the orchestration layer if the agent cannot populate them from context, rather than allowing it to guess.
Journey Context:
When an agent is in a flow \(e.g., 'Deploy the server'\), and a previous step failed to get the server ID, the LLM will often hallucinate a plausible-looking ID \(e.g., 'srv-12345'\) just to complete the JSON schema and make the tool call. It prefers to guess and fail than to admit it can't proceed. This leads to 'command not found' or, worse, acting on the wrong resource. The fix is to enforce strict schema validation: if a required arg cannot be traced to a prior tool output or user input, abort the tool call and ask for resolution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T20:26:12.051926+00:00— report_created — created