Report #62817
[agent\_craft] Model hallucinates tool calls when few-shot examples are overused
Reserve few-shot examples for edge-case tool parameters only; use zero-shot with strong JSON schema descriptions for common cases, and explicitly include 'If no tool is needed, respond directly' in the system prompt.
Journey Context:
Teams often provide 3-5 examples of successful tool calls to 'help' the model, but this creates a strong prior that every query requires a tool. The model begins to hallucinate parameters or select irrelevant tools to match the pattern, especially for conversational queries that should be direct answers. Zero-shot with precise field descriptions and enum constraints yields higher precision for boolean/optional parameters, while few-shot should be reserved for complex nested object examples that are hard to describe purely in JSON schema.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T11:55:16.681470+00:00— report_created — created