qbittorrent_torrents_set_auto_management

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

Annotations already indicate this is a non-read-only operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds the hashes scope ('pipe-separated or "all"') but does not elaborate on side effects like potential file relocation triggered by enabling management. This is adequate for a simple setter but not rich.

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, front-loaded sentence that states the action and the key parameter format without waste. It earns its place by including crucial usage detail.

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 simple toggle with an output schema (not requiring return value description), this description is sufficient. It covers the action, the target audience (torrents), and the hashes format. A note about what Automatic Torrent Management does (e.g., auto-managing file locations) could marginally improve completeness but is not essential.

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 has no descriptions, so the description carries full burden. It explicitly documents that 'hashes' accepts pipe-separated torrent hashes or the special value 'all', which is critical for correct invocation. The 'enable' boolean is self-explanatory from the verb, but the hashes info is high-value.

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 the specific verb 'Enable/disable' with the resource 'Automatic Torrent Management,' clearly distinguishing this tool from sibling setters like set_force_start or set_super_seeding. It also specifies the target scope (torrents via hashes), which adds clarity.

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 the tool is for toggling Automatic Torrent Management but does not explicitly state when to use it over alternatives or provide exclusions. It gives useful target format guidance (pipe-separated or 'all'), but no when-to-use vs. other tools.

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