download_gpx_file

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

With no annotations, the description carries the burden and does well by disclosing conversion behavior, the optional output_path side effect, and the return format (JSON string with base64 content when no path is given). It does not mention error cases or permissions, but for a read-only download this is adequate.

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 well-organized with Args and Returns sections and is appropriately sized. The first two sentences are slightly redundant ('Download activity as a GPX file' and 'Converts and downloads...'), but overall it is efficient and clear.

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 2-parameter tool with an output schema, the description covers the essential behavior, return type, and parameter semantics. It could mention error conditions, but the provided information is sufficient for an agent to select and invoke the tool correctly.

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 100%, and the description's Args section essentially restates the schema with an added example path. It adds minimal semantic value beyond the schema, so the baseline score of 3 is appropriate.

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 opens with 'Download activity as a GPX file,' a specific verb+resource+format statement that clearly distinguishes this tool from siblings like download_fit_file. It also mentions conversion to GPX, reinforcing the tool's unique role among download-related tools.

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 when to use the tool ('compatible with most GPS devices'), but it does not explicitly contrast it with alternatives like download_fit_file or download_activity_file. There is no when-not-to-use guidance or named alternative tool.

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