Report #20910
[synthesis] Agent hallucinates optional parameters or invents values for required parameters that don't exist in the tool's schema, causing the tool execution to fail silently or throw a validation error
Enforce strict JSON schema validation on agent outputs before tool execution. If validation fails, feed the exact schema error back to the agent as an observation, rather than a generic 'tool failed' message.
Journey Context:
LLMs often try to 'guess' parameters to satisfy what they think the tool wants, or they pass null to required fields. Generic error messages like 'Error executing tool' lead the agent to try a completely different tool. Returning the precise JSON schema violation \(''path'' is a required string, got integer'\) forces the agent to correct its syntax and retry correctly, turning a silent failure into a self-correcting feedback loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:30:35.330766+00:00— report_created — created