get_trade_destinations

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

Annotations indicate readOnlyHint=true, and the description adds that the tool shows domestic and international destinations. This is consistent and provides useful behavioral context beyond the annotation. No contradictions.

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 extremely concise, with three sentences that front-load the purpose and efficiently cover usage, parameter, and follow-up action. Every sentence earns its place.

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 the output schema exists (so return values are documented), the description adequately covers the input parameter, scope (domestic/international), and next steps. It could mention edge cases (e.g., no movement points), but for a simple list tool it is sufficient.

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?

With 0% schema description coverage, the description fully explains the lone parameter unit_id as 'The trader's composite ID (from get_units output)', adding essential meaning that the schema lacked.

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 clearly states the tool lists valid trade route destinations for a trader unit, specifying both domestic and international options. The verb 'List' and resource 'trade route destinations' are specific. It distinguishes from related tools like get_trade_options and get_trade_routes by focusing on valid destinations for a given trader unit.

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 explains when to use the tool (to see destinations for a trader) and provides follow-up instructions (use unit_action to start a route). It does not explicitly mention when not to use it or compare with siblings, but the context is clear.

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