Report #40227
[research] Agent silently fails or hallucinates parameters after an external API or tool schema updates
Inject tool schema validation into the observability layer. On every tool span, validate the LLM's generated arguments against the JSON schema of the tool before execution. Log 'ToolSchemaViolation' telemetry.
Journey Context:
APIs change \(e.g., a required field is added\). The LLM doesn't know this until it reads updated docs or errors out, and often it will just guess or omit the new field, leading to 400 Bad Request errors or silent data corruption. Catching this at the execution boundary via schema validation provides immediate, high-signal telemetry on schema drift, decoupled from the LLM's reasoning logic.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T21:59:41.107404+00:00— report_created — created