download_file

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

With no annotations, the description should disclose behavioral traits (e.g., overwrite behavior, error handling, authentication). It only states 'download' without any such details, leaving significant gaps for a tool that likely performs a side effect (file download).

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 concise (12 words) but at the expense of completeness. It lacks essential details, so while it is brief, it sacrifices clarity and usefulness.

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 no output schema and simple parameters, the description should explain what a 'track file' is and how the two parameters interact. It fails to do so, leaving the tool's behavior underspecified for an agent.

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?

The input schema has 0% description coverage, yet the description adds no meaning for the two parameters (fileId, fileName). For a tool with two parameters, this is a critical omission; the agent cannot infer how to use fileName or what fileId represents beyond being required.

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 action ('Download') and the resource ('Riverside track file') and specifies the destination ('configured local download directory'). However, it does not distinguish this tool from sibling tools like 'download_export' or 'download_timeline', leaving ambiguity about when to use each.

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 its siblings (e.g., download_export, download_timeline). There are no use-case conditions, prerequisites, or exclusions, making it difficult for an agent to select it correctly.

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