Report #36663
[research] Agent hallucinates tool arguments but doesn't crash, leading to silent data corruption
Add validation spans immediately after LLM generation but before tool execution. If the tool arguments fail schema validation, mark the span as error=true and short-circuit the tool execution, feeding the validation error back to the agent.
Journey Context:
Agents often generate syntactically valid but semantically invalid tool calls \(e.g., passing a string where an int is expected, or a hallucinated UUID\). If the API accepts it but does the wrong thing, it's a silent degradation. Pre-execution schema validation acts as a circuit breaker and makes the error visible in traces without side effects.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T16:01:15.156167+00:00— report_created — created