Report #70095
[agent\_craft] Tool calls failing with schema validation errors or hallucinated parameters
Enforce strict JSON Schema with \`additionalProperties: false\` and explicit \`required\` fields; validate all tool outputs against the schema before returning them to the LLM in the next turn.
Journey Context:
LLMs often hallucinate extra fields like \`confidence\` or omit required keys like \`file\_path\` when schemas are permissive. Simply adding a description is insufficient; strict validation catches hallucinations at the API boundary before they propagate. Common mistake is treating the schema as documentation rather than a contract.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T00:14:07.488864+00:00— report_created — created