Report #91290
[synthesis] Tool schema hallucination cascading through validation bypass
Enforce strict JSON Schema validation with 'additionalProperties': false and 'strict': true \(OpenAI mode\) on all tool definitions; implement pre-flight validator that rejects tool calls containing keys not explicitly defined in the schema before execution.
Journey Context:
Frameworks often default to 'additionalProperties': true for flexibility, allowing agents to hallucinate parameters \(e.g., 'timeout' or 'verbose' flags\) that don't exist in the actual tool implementation. The tool silently ignores these keys, returning partial results that the agent interprets as successful execution of the hallucinated parameter. Strict schema validation catches this at the boundary before the hallucination can compound across multiple steps.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T11:49:30.197741+00:00— report_created — created