download_torrent

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

The description reveals internal steps (token acquisition, file save) and return value (path or error). It does not mention permissions or side effects, but for a download tool, this is adequate. No annotations are present, so description carries the full burden.

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 with a clear header and structured details (Args, Returns). It is front-loaded with the main action. Slightly verbose in explaining process, but overall efficient.

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 one parameter, no annotations, and an existing output schema, the description covers the tool's purpose, process, parameter, and return value. It could include more on error handling, but it is sufficiently complete for this simple tool.

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 single parameter 'torrent_id' has no schema description, but the description adds meaning by specifying it is numeric and giving an example ('1125330'). This compensates for the 0% schema coverage.

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 a .torrent file for the given torrent ID,' which is a specific verb and resource. It distinguishes from siblings 'get_torrent_detail' and 'search_torrents' as these serve different purposes.

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 outlines the process (obtain token, download, save to directory) and implies use for downloading torrent files. It does not explicitly state when not to use or alternatives, but the context is clear enough.

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