Key points
- Tool descriptions are the primary mechanism for tool selection; minimal descriptions cause misrouting among similar tools.
- Descriptions should include input formats, example queries, edge cases, and boundary explanations.
- Near-identical descriptions (analyze_content versus analyze_document) cause requests to land on the wrong tool.
- Keyword-sensitive wording in the system prompt can create unintended tool associations.
- Generic catch-all tools lack clear input/output contracts.
Common misconceptions
- "The tool name is enough for the model to choose." The description carries the real signal.
- "Few-shot examples are the first fix for misrouting." Fix the descriptions first; examples add tokens to every call.
- "One flexible tool is simpler than several specific ones." Its outputs become unpredictable.
Watch for
One-line descriptions, two tools that could be swapped without anyone noticing, and prompt phrases that trigger a tool on a single keyword.
Practice Task 2.1
Start with the free 10-question check to see where you stand across all five domains. In CCA Prep Studio, 57 practice items cover this task, each tracked toward your mastery score.