Report #85132
[synthesis] Models hallucinate or crash on ambiguous tool calls with missing parameters
Explicitly define default behavior in the tool description. For GPT-4o, add 'NEVER hallucinate values; return an error if missing'. For Claude, add 'If a required parameter is missing, ask the user'. Never rely on the model's implicit behavior.
Journey Context:
GPT-4o defaults to 'helpful' by fabricating plausible IDs/paths to avoid breaking the flow, causing silent downstream failures. Claude defaults to 'harmless' by halting and asking, causing UX friction. Gemini passes null, causing type errors in strict environments. You cannot use a single generic prompt to fix this; you must tailor the tool description's error handling instruction per model to prevent silent data corruption vs. loop stalling.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T01:28:52.194770+00:00— report_created — created