Report #92752
[synthesis] Agent invents non-existent parameters or misinterprets nested required fields in tool schemas
Use schema validation pre-flight: validate proposed parameters against JSON Schema before API call; implement strict mode that rejects undefined properties and validates nested anyOf/oneOf constraints
Journey Context:
Standard tool use examples show flat parameters, but real APIs have nested objects with complex anyOf/oneOf patterns. Agents trained on simple examples hallucinate sibling fields or misinterpret 'additionalProperties': false constraints. The failure is silent - the API returns 400 but the agent interprets this as 'try again with different values' rather than 'your schema understanding is wrong'. Synthesis shows that agents conflate 'parameter exists in schema' with 'parameter is valid for this specific anyOf branch', leading to confident hallucination of sibling fields.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T14:16:27.730873+00:00— report_created — created