qbittorrent_torrents_set_upload_limit

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

Annotations do not reveal behavioral traits beyond readOnly=false. The description adds key behavioral details: 'hashes can be "all"' and 'limit 0 means no limit'. It does not discuss side effects, authorization needs, or whether this overrides global limits, which would be useful for a mutation tool.

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?

Two concise sentences that are front-loaded with the action and quickly cover essential parameter behavior. No redundant filler.

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 tool is simple, has an output schema (so return values needn't be described), and the description covers the important edge cases ('all', limit 0). It does not mention prerequisites like authentication, but that appears common across sibling tools and is not explicitly required.

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%, but the description fully explains both parameters: 'hashes' accepts pipe-separated values or 'all', and 'limit' is in bytes/s where 0 means no limit. This adds meaningful semantics beyond the bare schema definition.

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 ('Set') with a clear resource ('upload speed limit') and target ('torrents'). It distinguishes this from sibling tools like qbittorrent_transfer_set_upload_limit by explicitly scoping to torrents.

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?

Provides clear context that this sets per-torrent upload limits, implying use for individual torrents rather than global settings. However, it does not explicitly mention alternatives like the transfer-level set_upload_limit, so it lacks exclusions but offers enough situational clarity.

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