download_course_gpx

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

The description implies a local file write via the output_path parameter, but it does not explicitly disclose side effects, whether it modifies Garmin data, or any required permissions. With no annotations, this lack of explicit behavioral detail leaves uncertainty.

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 highly succinct, using only two sentences to convey the tool's purpose and parameter details. No redundant or verbose language is present.

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 action and all parameters, making it usable. However, it does not mention what the function returns (e.g., success status or saved file path), even though an output schema exists. This is a minor gap but does not prevent basic usage.

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?

Both parameters are described in the docstring: course_id is the ID of the course, and output_path is the optional local destination with a clear default. The meaning and usage of each parameter are fully explained.

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 tool downloads the exact official GPX file for a Garmin Connect course. It uses a specific verb ('Download') and a specific resource ('GPX file for a Garmin Connect course'), making the purpose unambiguous.

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 like download_workout or download_activity_file. There is no mention of scenarios where this tool is preferred or any comparison with sibling tools.

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