Report #82352
[synthesis] Agent hallucinates the existence of a tool or API to solve a problem, and subsequent steps build a complex plan around it
Intercept tool calls against a strict allowlist before execution, and return a standardized Tool not found error that forces the agent to re-plan using available tools.
Journey Context:
When an agent faces a task it cannot solve with its current toolset, it often hallucinates a tool name that sounds plausible \(e.g., search\_database instead of run\_sql\). Because the LLM is confident this tool exists, it builds a multi-step plan relying on its output. If the framework silently fails or if the error message is vague, the agent might assume the tool worked but returned empty. The fix requires strict schema enforcement at the router level and explicit error messages that trigger replanning rather than continuation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T20:49:15.838120+00:00— report_created — created