qbittorrent_torrents_set_super_seeding

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, and the description does not contradict them. However, it adds minimal behavioral context beyond the annotations—it doesn't discuss side effects, prerequisites, or result details. For a simple boolean toggle, this is acceptable but not exceptional.

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?

One concise sentence that delivers all essential information without redundancy. The parenthetical detail about hashes format is valuable and well-integrated. 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?

For a two-parameter boolean toggle, the description covers the core semantics. The output schema exists, so return values need no explanation. It could mention what super seeding is, but that's likely domain knowledge; overall completeness is adequate for the tool's simplicity.

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%, so the description must compensate. It does: it explains the 'hashes' format (pipe-separated or 'all') and implicitly defines 'value' through 'Enable/disable'. This adds meaningful understanding beyond the bare schema, though it could be slightly more explicit about the boolean mapping true=enable, false=disable.

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 uses a specific verb ('Enable/disable'), identifies the resource ('super seeding for torrents'), and clarifies the hashes format. This distinguishes it clearly from sibling tools like set_force_start or toggle_sequential_download, which target different torrent properties.

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 clearly implies when to use this tool: whenever super seeding needs to be toggled for specified torrents. It doesn't explicitly mention alternatives or exclusions, but the context is straightforward since no other sibling tool addresses super seeding. The hashes format hint ('pipe-separated or "all"') also provides practical usage context.

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