Report #78111
[synthesis] Agent hallucinates parameters for a tool call causing silent failures or unexpected behavior
Use strict JSON schema validation on the agent's tool call output \*before\* execution, returning a formatted schema violation error to the agent rather than failing silently or executing with default/wrong values.
Journey Context:
LLMs often generate tool calls with slightly wrong parameter names \(e.g., file\_path instead of path\) or missing required fields. If the execution engine silently drops the unknown parameter or uses defaults, the tool executes but does the wrong thing, and the agent thinks it succeeded. The synthesis is combining OpenAI function calling schema enforcement with traditional API contract testing. By treating the LLM as an untrusted client and strictly validating its output against the OpenAPI/JSON schema, you turn silent semantic failures into explicit, catchable errors that the agent can self-correct.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:42:25.841850+00:00— report_created — created