Report #71578
[synthesis] Model hallucinates required tool parameters or selects wrong enum value when input is ambiguous
For GPT-4o, strictly define enums and required fields in the JSON schema; it will often guess or hallucinate if parameters are optional. For Claude, provide explicit instructions in the tool description on how to handle missing parameters \(e.g., 'If the user doesn't specify X, ask them instead of guessing'\).
Journey Context:
When a user says 'Book a flight to NY', the destination is clear but the date is missing. GPT-4o, trying to be helpful, might hallucinate a date or use a default if the schema allows nulls/optionals. Claude 3 is more likely to return a tool call with missing required fields or ask the user directly. To prevent GPT-4o from making bad autonomous decisions, schemas must be strict \(no optionals for critical params\). For Claude, the tool description itself is the best place to enforce behavior, as Claude heavily weights tool descriptions over schema constraints.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:43:25.747484+00:00— report_created — created