download_workoutDownload a workout as a FIT file by providing its workout ID, ready for syncing to a Garmin device.
Download a workout in FIT format for syncing to a Garmin device.
| Name | Required | Description | Default |
|---|---|---|---|
| workoutId | Yes | The unique workout identifier (required) |
Changes observed during successful MCP inspections.
v4.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds value by specifying the FIT format and Garmin sync purpose, which are not in annotations. 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?
A single, efficient sentence that conveys the essential information without extraneous text. Front-loaded with the core action and format.
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 single-parameter tool with no output schema, the description covers the main purpose and format. It does not detail the exact response shape (e.g., binary or base64), but the mention of 'FIT format' gives sufficient context. Overall, adequately complete for its complexity.
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 documents workoutId with a clear description and is the only parameter, achieving 100% coverage. The description adds no additional detail about the parameter beyond what the schema provides, so baseline 3 applies.
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 action (download), the resource (workout), and the output format (FIT) for a specific purpose (Garmin sync). It distinguishes from siblings like download_activity or get_workouts by focusing on the downloadable file 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?
The description implies usage context—syncing to a Garmin device—which tells the agent when this tool is appropriate. However, it does not explicitly contrast with alternatives like get_workout_by_id or schedule_workout, so it falls short of full guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.