download_workout

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

No annotations exist, so the description carries the full burden. It only states the action and output format, omitting behavioral traits like authentication requirements, error behavior for invalid IDs, or whether the operation is read-only. The concise phrase does not address these critical aspects.

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 short (one phrase) and front-loaded with the action. It is concise but lacks structure—no sentences, no breakdown of key details. While it's not verbose, it could be more informative without sacrificing brevity.

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 single parameter, presence of an output schema, and many sibling tools, this description is insufficient. It does not explain the output format beyond the phrase, nor does it cover constraints (e.g., only for own workouts, size limits). An agent may lack enough context to use the tool correctly in all scenarios.

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 0%, and the description adds no parameter-level meaning. While 'workout_id' is somewhat self-explanatory, the tool should clarify what constitutes a valid ID (e.g., from get_workouts) or any constraints. The description falls short of compensating for the missing schema descriptions.

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 specific action ('download'), resource ('workout plan'), and output format ('FIT file (base64)'). This distinguishes it from sibling tools like get_workout_by_id or get_workout_templates, which serve different purposes.

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 provides no guidance on when to use this tool versus alternatives, such as when a raw FIT file is needed versus structured JSON data. No exclusions, prerequisites, or contextual hints are given.

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