Report #94488
[synthesis] Models Hallucinate or Fail on Missing Tool Call Parameters Differently
Provide explicit default values or make parameters optional in the JSON schema for GPT-4o to avoid hallucinated fills, but strictly validate on the application side for Claude to catch its hard failures.
Journey Context:
GPT-4o tries to be helpful by guessing missing parameters, leading to silent logical errors downstream. Claude strictly adheres to the schema and will throw an API error or refuse to call the tool if it cannot fulfill a required parameter. Gemini might just output the JSON as text. You must handle these divergent failure modes: validate GPT-4o's output to catch hallucinations, and catch Claude's API errors to retry with more context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T17:11:01.547564+00:00— report_created — created