Export Segment as GPX

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description adds real value: the return format (GPX XML) and a non-obvious API limitation (no route upload support, manual import required). It does not mention size/pagination behavior for the returned XML, keeping it just short of a 5.

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?

Three tight sentences with the core action front-loaded, followed by output format and then the important caveat. Nothing is redundant or padded.

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 one-parameter export tool with rich annotations, the description covers purpose, return format, downstream compatibility, and the manual-import limitation. No output schema is needed because the description already states the return type.

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% and the single segment_id parameter is fully documented in the schema. The description adds no parameter-level meaning beyond what the schema already provides, which is the expected baseline here.

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+resource+format: 'Export a Strava segment as a GPX file for navigation.' This distinguishes it from the route-export siblings by naming the resource (segment) and the output format (GPX), though it never explicitly contrasts with strava_export_route_gpx or strava_export_route_tcx.

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 usage context ('for navigation', 'imported into Garmin Connect, Coros') and a note that imports must be manual. However, it gives no explicit guidance on when to choose this over the sibling route exporters or the TCX variant; the selection logic is left to inference.

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