remove_torrent

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

Discloses the plugin dependency and effect of delete_data, but lacks details on irreversibility or response behavior. No annotations to supplement.

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 short, focused sentences. No wasted words; front-loaded with core action, then critical caveat.

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?

Covers main action and key behavioral detail, but omits return value, confirmation, or error scenarios. Acceptable given low parameter count and no output schema.

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%, but description clarifies meaning of `hashes` (torrent hashes) and `delete_data` (boolean, deletes files). Does not specify hash format or constraints.

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?

Clearly states 'Remove torrents' and specifies the optional data deletion effect. Distinct from sibling tools like add_torrent or list_torrents.

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?

No explicit when to use or alternatives, but mentions the plugin requirement for delete_data, providing some usage context.

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