Report #103071
[architecture] Tool use reliability: my agent calls the wrong tool or hallucinates arguments
Enforce tool schemas at runtime, validate arguments with a second pass \(JSON Schema or a small validator model\), and never expose effectful tools to a planning step that hasn't been approved. Prefer deterministic routing or explicit confirmation for high-stakes actions.
Journey Context:
LLMs choose tools reliably in simple demos but drift when tool lists grow, descriptions overlap, or context pressure increases. Defense in depth is the only practical fix: strict JSON schemas for every tool, argument validation before execution, tool-result feedback loops so the model can self-correct, and a clear separation between read-only diagnostic tools and write-only action tools. The highest-stakes operations should require an explicit approval workflow rather than trusting model intent, because a wrong argument to a production API can be far more expensive than a wrong answer.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-10T04:57:58.132849+00:00— report_created — created