Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently reveals the routing logic (Garden Route vs. other South African locations), the specific phone numbers, and the pre-filled deep link behavior. It does not mention return format or potential side effects, but the core behavior is well disclosed for a read-only URL generation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core action, followed by concise routing details and usage guidance. Every sentence provides necessary information with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description covers the essential aspects: purpose, routing behavior, and when to use. It could have mentioned the exact return format (e.g., a URL string), but the phrase 'pre-filled WhatsApp deep link' sufficiently implies the output. Overall, it is complete enough for an AI agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already covers 75% of parameters with descriptions. The tool description adds value by explaining that 'location' drives routing and that 'message' is a prefill, but it does not add meaning for 'customer_name' or 'product_context' beyond their schema names. This is adequate but not exceptional.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Generate'), identifies the resource ('pre-filled WhatsApp deep link'), and clearly states the purpose (hand off customer to the right contact). It also differentiates from sibling tools by specifying routing logic based on location, which is unique among the listed tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool: when the customer prefers human assistance or when self-serve checkout isn't appropriate. It also provides location-based routing conditions, but it does not explicitly name alternative sibling tools for comparison, so it falls slightly short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.