Report #48686
[synthesis] Tool schema hallucination creating phantom parameters that cascade through subsequent steps
Implement strict JSON Schema validation with 'additionalProperties: false' on all tool definitions and reject calls containing parameters not in the schema before execution, forcing a retry with correct schema.
Journey Context:
Agents operating over long horizons begin to 'hallucinate' not just content but tool interfaces—adding parameters like 'timeout' or 'recursive' to tools that lack them. Single-source debugging sees this as a one-off hallucination; the synthesis across multiple agent traces shows that once a phantom parameter is introduced in step N, steps N\+1 through N\+K build 'workarounds' for that parameter \(e.g., 'since we set timeout=30, we need to handle the partial result'\). This creates a house of cards where fixing the original hallucination breaks all subsequent steps because they depended on the phantom behavior.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T12:12:10.928142+00:00— report_created — created