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

Annotations already mark this as read-only, idempotent, and non-destructive, so the bar is lower. The description adds valuable behavioral context beyond annotations: route availability by shipping region, discount differences, affiliate commission tracking, no price markup, behavior when country is omitted, and the quote-basis exclusion. No contradiction with annotations.

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 longer than average, but every sentence carries decision-relevant information: purpose, required parameter behavior, edge-case behavior, affiliate disclosure, and alternative tool routing. The critical 'PASS THE BUYER'S SHIPPING COUNTRY' instruction is front-loaded right after the purpose statement.

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 there is no output schema, the description fully compensates by explaining the return behavior with and without the country parameter, the regional shipping constraints, the quote-basis models case, and the affiliate/pricing caveats. An agent has everything needed to call this tool correctly and interpret its result.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that country 'routing and any discount depend on it', that omitting it returns both routes, and that the country is the shipping country, not the buyer's billing country. The model parameter gains no extra description, but the country semantics are substantially enriched.

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?

States a specific verb and resource: 'Get the purchase route for a robot model', and immediately clarifies the deliverable as 'a botinfo.ai URL that resolves to a dealer checkout, plus the live comparison-board page'. It also distinguishes itself from the sibling request_quote by explaining when no route is returned and that request_quote should be used instead.

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?

Provides explicit when-to-use guidance: pass the buyer's shipping country because routing and discount depend on it, and explains the consequence of omitting it. It also gives an explicit exclusion and alternative: 'Returns no route for quote-basis models; use request_quote instead.'

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