get_exercise_gpx

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

The description notes that GPX contains route/track data and can be used with mapping applications, adding context beyond the schema. However, with no annotations, it does not disclose authentication needs, rate limits, or any other behavioral traits.

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 concise with two sentences, no extraneous information, and the key action is front-loaded.

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 low complexity (1 parameter, no output schema, no annotations), the description is adequate. However, it does not specify the return format of the GPX data (e.g., binary string) or mention any pagination or size limits, leaving some gaps.

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 covers 100% of the single parameter (exerciseId) with a description implying it is required. The tool description repeats this requirement but adds no additional meaning beyond what the schema provides.

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 verb 'Download', the resource 'exercise GPS route', and the format 'GPX'. It distinguishes from sibling tools like get_exercise_fit and get_exercise_tcx by specifying the GPX format.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that other formats like FIT or TCX are available via sibling tools, nor any criteria for choosing GPX.

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