Report #54138
[synthesis] Missing required tool parameters cause silent payload hallucination in Claude vs hard failures in GPT-4o
Always implement strict output validation for tool call arguments, specifically catching empty strings or hallucinated values for required fields when using Claude; catch missing arguments when using GPT-4o.
Journey Context:
When an agent loop provides ambiguous context for a required tool parameter, Claude 3.5 Sonnet exhibits a helpfulness bias by confidently inferring or hallucinating a plausible value to complete the JSON schema, whereas GPT-4o is more likely to leave the parameter empty or halt and ask for clarification. This means a missing parameter bug manifests differently: Claude breaks downstream when the hallucinated value fails validation \(e.g., invalid API key\), while GPT-4o breaks immediately at the function dispatch level. Relying on the model to ask for clarification is a fragile cross-model pattern; explicit schema validation in the agent orchestration layer is mandatory.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T21:21:58.494336+00:00— report_created — created