Pause, Resume, or Label a Torrent

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

The description adds 'Reversible' beyond the annotations, providing helpful extra context. Annotations already indicate it is not read-only and not destructive, but the reversibility claim is a useful additional trait. However, it does not disclose other potential side effects or permission requirements.

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 a single sentence that lists all operations and adds a relevant note about reversibility. 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?

The description covers the core operations but does not specify which parameters are required for each operation (e.g., label for set_label) or provide return value/error behavior. Given the 4-parameter schema and lack of output schema, some gaps remain, but the tool is simple and annotations help.

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%, and the description compensates by explaining that 'label' means category and by mentioning the seed-ratio limit. It also lists the operation enum values in prose. The torrentId is self-explanatory, and operation details are covered by the enum.

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 tool's function with a specific verb and resource: pausing, resuming, setting label/category, or setting seed-ratio limit on a torrent. It distinguishes itself from sibling tools like whatbox_torrent_add, whatbox_torrent_remove, and whatbox_torrents_status.

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 clear context by listing the operations, implying it should be used when these actions are desired. It does not explicitly mention alternatives or exclusions, but the phrase 'one torrent' and the operation list give sufficient guidance.

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