qbittorrent_torrents_set_download_limit

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

Annotations already indicate this is a mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds meaningful semantic context (bytes/s unit and 0 meaning no limit), but does not disclose additional behavioral traits such as whether the operation applies to all torrents at once or any side effects. With annotations present, this is adequate 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?

The description is a single, tightly written sentence that front-loads the core action and immediately defines the two key parameters. Every word earns its place with no redundancy or fluff.

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 simplicity of the tool, the description covers the essential behavioral and parameter semantics. The presence of an output schema reduces the need to explain return values. The combination of annotations, schema, and description provides a complete picture for an agent to select and invoke the tool correctly.

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 input schema provides no descriptions (0% coverage), so the description fully compensates. It explains the format and special value for 'hashes' (pipe-separated or 'all') and the meaning of 'limit' (bytes/s; 0 = no limit). This provides crucial meaning beyond the raw schema fields, covering both required parameters.

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 action ('Set download speed limit') and resource ('torrents'), and the mention of 'hashes' distinguishes it from global transfer-level limit setters like qbittorrent_transfer_set_download_limit. It uses a specific verb and specifies the scope, making it unambiguous.

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 usage context: it explains the special value 'all' for hashes and clarifies that limit 0 disables the limit. While it does not explicitly mention alternative tools or exclusion criteria, the per-torrent scope is clear from the wording, which is sufficient for this simple setter.

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