Report #82988
[synthesis] Agent confidently makes multiple consecutive wrong API calls due to a single hallucinated parameter type
Enforce strict schema validation with early exit and self-correction on the \*first\* tool call failure, rather than allowing the agent to 'adapt' the failed output into the next step.
Journey Context:
When an agent hallucinates a parameter \(e.g., passing a string where an int is expected\), the API returns an error. The agent, trying to be helpful, often interprets the API error message as a \*new\* data point rather than a hard failure, and attempts to 'fix' it by passing the error string into the next tool. This creates a cascade of confidently wrong steps. Developers often let the agent retry, but the context is already poisoned by the hallucinated assumption. Hard failing and resetting the step's context is necessary.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T21:53:18.984002+00:00— report_created — created