Report #42421
[synthesis] Agent hallucinates parameters for dynamically loaded tools it has never seen before
When dynamically loading a new tool, force the agent to first output a tool understanding step where it paraphrases the tool's schema and constraints before generating the execution JSON.
Journey Context:
When an agent searches a tool registry and pulls a new API spec, it often immediately attempts to call it. The LLM relies on its pre-training for common API patterns \(e.g., assuming a limit parameter exists\). If the dynamic tool uses max\_items, the call fails. Forcing the agent to read and paraphrase the schema shifts it from pattern-matching to actual comprehension of the provided spec.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T01:40:29.560074+00:00— report_created — created