download_activity

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

No annotations provided, so description carries full burden. It states 'download' but does not clarify whether this is a read-only operation, what authentication or permissions are needed, or if there are any side effects. Minimal behavioral disclosure.

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?

Single sentence that front-loads the core purpose and lists formats succinctly. No redundant or filler content.

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 simple download tool with two parameters and no output schema, the description is mostly adequate. However, it lacks information about the return type (e.g., binary file, URL) or pagination/rate limits, which could be valuable for agent invocation.

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%, with both parameters documented. The description lists formats that are already in the schema's description for 'format', adding no new meaning beyond restatement. 'activityId' is only described as 'required' in schema; description does not enhance it.

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?

Description clearly states the verb 'download', resource 'activity', and specific formats (FIT, TCX, GPX, KML, CSV). Immediately distinguishes this tool from siblings like upload_activity, create_manual_activity, or delete_activity by focusing on export.

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?

Description implies usage for downloading activity data in specific file formats, but does not explicitly state when to use this tool versus alternatives like download_workout (which downloads workout data). No exclusionary guidance or context for when not to use it.

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