qbit_delete_torrent

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

No annotations exist; the description carries the full burden. It reveals the dry-run preview and optional file deletion, but does not explain what 'remove' entails (e.g., stopping downloads, removing metadata) or mention prerequisites, permissions, or reversibility. Moderate transparency.

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 only four lines: a concise purpose statement followed by three single-line parameter explanations. No unnecessary words, clearly organized, and front-loaded with the main action.

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 three parameters and no schema descriptions, the description covers the essential functionality and parameter usage. It lacks details on error handling or prerequisites (e.g., torrent must exist), but is otherwise complete for a deletion tool with a dry-run feature.

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 has 0% description coverage, so the description must add all meaning. It explains that hash accepts a full hash or unique prefix, confirm controls real deletion vs dry-run, and delete_files removes associated files from disk. This fully compensates for the missing schema descriptions.

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 'Remove a torrent from qBittorrent by hash', specifying a concrete verb and resource. Among sibling tools, it is the only delete operation, making its purpose distinct and unambiguous.

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 explains how to use the confirm and delete_files parameters, including the dry-run behavior for confirm=False. However, it does not compare with sibling tools like qbit_pause to guide when to delete vs pause, which would strengthen usage guidelines.

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