Report #98807
[agent\_craft] Model calls the wrong tool or ignores available tools
Write every tool description as a trigger condition: 'Use X when Y.' Include when NOT to use it, expected input shape, and what to do on ambiguity. Keep namespace descriptions short and put behavioral detail in the function description.
Journey Context:
Teams often name tools 'get\_user\_info' and describe them as 'Gets user info,' which gives the model no decision boundary. OpenAI's function-calling best practices explicitly tell you to 'describe when \(and when not\) to use each function' and to 'explicitly describe the purpose of the function and each parameter.' The model selects tools by matching the situation in the prompt to the situation in the description, so the description should read like a policy, not a label.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-28T04:49:04.125194+00:00— report_created — created