qbittorrent_transfer_set_download_limit

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

The description discloses that a limit of 0 removes the limit, which is relevant behavior beyond the annotations' basic read/write and destructiveness hints. It adds value by specifying units and the 0 semantics.

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?

A single sentence with all necessary information, no redundancy.

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 one-parameter setter, the description covers the purpose, the parameter meaning, and the edge case of 0. The existence of an output schema avoids the need to describe return values.

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 provides only a naked integer 'limit' with no description, but the description fully defines it as a download speed limit in bytes/s and explains the special value 0.

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 identifies the action ('Set'), the target ('global download speed limit'), and includes units and behavior for 0, distinguishing it from per-torrent and upload counterparts.

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 word 'global' provides clear context that this sets the all-client limit rather than per-torrent, but it does not explicitly name alternatives or exclusions.

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