Strava Route

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds useful behavioral context by explaining that summary/structured modes avoid full route geometry, which is a privacy-relevant behavior beyond what annotations provide. 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 two short sentences, immediately front-loaded with the core purpose. Every word adds value, with no fluff or repetition.

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?

For a simple get-by-id tool with an output schema and robust annotations, the description is fairly complete. It covers the primary purpose and the key mode distinction. It could be improved by explicitly noting that raw mode requires explicit_user_intent, but that is already in the schema, so the description does not need to repeat it.

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 description coverage is 75%, with most parameters described. The description adds limited parameter insight beyond the schema; the phrase 'avoid full route geometry' clarifies privacy_mode behavior, but other parameters like response_format and explicit_user_intent are not addressed in the description. Baseline of 3 is appropriate.

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 'Get route details by id', using a specific verb and resource. It distinguishes from sibling tools like strava_list_routes by focusing on retrieving a single route by ID. The mention of modes adds clarity without confusion.

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 implies use when you have a route ID and need its details, but does not explicitly contrast with alternatives like strava_list_routes for finding routes. The note about summary/structured modes provides some usage context for privacy settings, but no explicit when/when-not guidance.

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