tp_download_workout_file

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Download a workout file' but does not mention side effects (e.g., whether the file is saved to output_path or returned as binary), any authentication requirements, or error behavior. This leaves significant ambiguity for the agent.

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 sentences, front-loaded with the primary action, and contains no fluff. Every word earns its place, making it an excellent model of conciseness.

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?

The description covers the core action and provides a source for file_id, but given the tool has 4 parameters and no annotations or output schema, it lacks important contextual details such as what happens if output_path is omitted or what the tool returns. The schema covers parameter descriptions, but the description does not fully explain the tool's overall behavior.

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%, so the baseline is 3. The description adds value by explaining the relationship between file_id and tp_get_workout, which is not fully captured in the schema's parameter descriptions. This extra context helps the agent understand how to fill the parameters correctly.

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 states a specific action: 'Download a workout file by file_id.' This clearly identifies the tool's function and differentiates it from sibling tools like tp_upload_workout_file and tp_delete_workout_file. It also provides a helpful pointer on obtaining the file_id, which enhances clarity.

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 by stating 'Get file_id from tp_get_workout device_files/attachment_files,' which tells the agent how to obtain a required parameter. It does not explicitly mention when not to use the tool, but the purpose is clear and no alternative download tool exists among siblings.

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