qbittorrent_torrents_delete

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, but the description adds crucial context: that delete_files=true irreversibly deletes downloaded data. This goes beyond the annotation by clarifying the exact destructive behavior and warning about irreversibility.

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 that are front-loaded with the core action. Every sentence provides value: the first states the verb and resource, the second explains key parameter nuances and a critical warning. No wasted words.

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, the description is complete: it covers the action, parameter format, special 'all' value, and the irreversible consequence. An output schema exists for return values, so no additional explanation is needed. The description matches the tool's complexity.

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 0%, but the description compensates by explaining both parameters: 'hashes is pipe-separated or all' for the hashes parameter, and the delete_files effect with its irreversibility. This fully covers the parameter semantics.

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 'Delete torrents' with a specific verb and resource. It distinguishes from sibling tools that manipulate torrents (e.g., pause, resume) by focusing uniquely on deletion. It also adds clarity on special inputs ('all') and the delete_files flag.

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 gives clear context on how to use the tool (pipe-separated hashes or 'all', delete_files behavior) but does not explicitly mention when to use it over alternative tools or provide exclusions. This is minor given the self-explanatory name.

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