download_c411_torrent

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

No annotations provided, so description carries full disclosure burden. Successfully discloses the side effect ('save to disk'), indicating filesystem mutation. However, lacks details on idempotency, network requirements, error handling (e.g., invalid hash), or output structure despite having an output schema available.

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, dense sentence with zero waste. Front-loaded with the action verb, immediately communicating purpose. Every clause earns its place: source domain, identification method, and persistence mechanism are all efficiently packed.

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?

Appropriate for a 2-parameter tool with full schema coverage and existing output schema. Covers the essential 'what' and 'where to' aspects. Minor gap: could briefly mention the return value indicates success/failure or file path since annotations are absent.

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%, establishing a baseline of 3. Description adds value by clarifying the infoHash's role in identifying the specific torrent to retrieve ('by its infoHash'), and implicitly connects the outputDir to the 'save to disk' action. Could mention the default /tmp behavior explicitly, but overall adds meaningful usage context.

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?

Excellent specificity: states the verb ('Download'), resource ('.torrent file'), source ('c411.org'), identifier ('by its infoHash'), and side effect ('save to disk'). Clearly distinguishes from siblings 'get_c411_torrent_info' and 'search_c411' through the explicit action of downloading vs retrieving metadata or searching.

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?

Provides implied usage context through the specific action ('download... save to disk'), but lacks explicit when-to-use guidance contrasting with siblings. Does not state prerequisites (e.g., valid c411.org infoHash) or error conditions.

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