Report #63726
[synthesis] Model hallucinates tool parameters or drops tool calls on ambiguous schema
Implement strict server-side validation of model-generated tool call arguments before execution. Do not rely on the model to self-correct or refuse: GPT-4o will hallucinate missing params, Claude will drop the call and ask the user, Gemini will throw an opaque error.
Journey Context:
Developers often assume LLMs will safely fail or ask for help when a tool schema is ambiguous or missing required parameters. Cross-model testing reveals divergent failure modes: GPT-4o confidently fills in garbage/dummy values to satisfy the schema, Claude 3.5 Sonnet often abandons the tool call entirely and outputs text asking for clarification \(breaking automated agents\), and Gemini fails silently or with API errors. Relying on model-side validation creates fragile, model-specific failure paths. The only robust cross-model pattern is to treat the model's tool call output as untrusted user input and validate it strictly in your orchestration layer, returning the validation error as a tool result to force a retry.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:26:58.587318+00:00— report_created — created