Remove a Torrent

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

Annotations already declare destructiveHint=true, but the description adds critical context: 'Requires explicit human approval' and 'deleting data is irreversible.' This goes beyond the structured hints and informs the agent of an approval step and permanent consequences.

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?

Two concise sentences lead with the verb and purpose, immediately state the optional deletion, and add the critical human approval warning. No filler or redundancy.

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 destructive tool with no output schema, the description covers the action, the optional data deletion, and the need for approval. It does not describe the return value or post-removal state, but these are likely obvious for a removal operation. Overall, it is sufficiently complete.

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 0%, so the description must compensate. It explains the deleteData parameter as 'optionally deleting its downloaded data,' but does not elaborate on torrentId beyond what its name implies. The description adds some semantic value but does not fully cover both parameters.

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 specific action: 'Remove a torrent from the client' and distinguishes it from siblings like whatbox_torrent_add, whatbox_torrent_control, and whatbox_torrents_status. It also mentions the optional deletion of downloaded data, which adds precision.

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 usage for removing torrents but does not explicitly state when to use this versus alternatives. It lacks exclusions or comparative guidance, though the purpose is self-evident among siblings.

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