remove_torrent

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It hints at a destructive action ('remove') and data deletion option, but lacks details on permissions, side effects, error handling, or what the output schema might return. This is insufficient for a mutation tool with potential data loss.

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 extremely concise with two sentences that directly convey the tool's function and a key parameter detail. It's front-loaded with the main action and wastes no words, making it efficient for an agent to parse.

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 the tool's complexity (a mutation with data deletion risk), no annotations, and an output schema (which may cover return values), the description is minimally adequate. It covers the basic action and a critical parameter but misses broader behavioral context, making it just viable for use.

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?

The description adds meaningful context for the 'delete_data' parameter by explaining its effect ('to also delete downloaded files'), which is valuable since schema description coverage is 0%. However, it doesn't clarify 'torrent_id' (e.g., format or source), leaving some parameter semantics incomplete.

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 action ('Remove a torrent') and specifies the resource ('torrent'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'delete_torrent' or 'forget_torrent', which appear to have similar functions, so it doesn't reach the highest score.

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 provides no guidance on when to use this tool versus alternatives like 'delete_torrent' or 'forget_torrent' from the sibling list. It mentions the 'delete_data' parameter but doesn't explain broader usage contexts, prerequisites, or exclusions, leaving the agent with minimal direction.

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