qbittorrent_torrents_pause

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the agent knows it's a mutating but non-destructive operation. The description adds 'Pause (stop)', which is consistent but doesn't go beyond the annotation by explaining side effects like stopping transfers or seeding behavior.

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, front-loaded with the action and includes essential parameter details. No unnecessary 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?

Given the simple operation, the description covers the essential aspects: what it does and how to specify targets. An output schema exists, so return values are structured separately. The description could mention the effect on torrents (e.g., stops downloading/seeding) but is otherwise adequate.

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 schema only defines 'hashes' as a string with no description. The description compensates fully by explaining that hashes is pipe-separated or accepts the special value 'all', which is critical for correct use.

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 explicitly states 'Pause (stop) torrents' with a clear verb and resource. It distinguishes from sibling tools like resume, delete, and recheck by specifying the action of pausing.

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 implies usage: pause torrents when you want to stop them. It does not explicitly mention when to use this instead of alternatives like delete or recheck, nor does it provide exclusions. The sibling context makes it somewhat clear, but no explicit guidance is given.

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