Report #85688
[synthesis] Tool schema hallucination cascading through verification steps
Enforce strict schema validation using jsonschema Draft 7 with 'additionalProperties': false before executing any tool call, reject outputs that pass JSON parse but fail schema compliance
Journey Context:
Most validation only checks if required fields exist, not if extra fields are present; LLMs often invent 'timeout' or 'retries' parameters for tools that don't support them; these pass JSON.parse\(\) but cause the tool wrapper to ignore the hallucinated args silently. The synthesis reveals that validation must occur at the semantic schema level, not just syntactic JSON level, and must explicitly forbid additional properties to catch hallucinated parameters.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T02:25:03.212488+00:00— report_created — created