qbittorrent_transfer_set_upload_limit

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

The description goes beyond the annotations by specifying units (bytes/s) and the special behavior of 0 (removes limit). This adds meaningful behavioral context not available from the schema or annotations, while being consistent with the non-read-only, non-destructive hints.

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 short, front-loaded sentence that contains no filler. Every word adds value, covering the action, resource, unit, and special value behavior.

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 with an output schema, the description covers the core functionality, units, and special value behavior. It is sufficient for an AI agent to correctly select and invoke the tool among many siblings.

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 description coverage is 0%, so the description fully compensates by explaining the unit of measure (bytes/s) and the semantic of 0 as 'remove limit'. This is crucial for correct invocation, though it does not document potential range constraints.

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 action ('Set'), the resource ('global upload speed limit'), and adds specificity ('in bytes/s', '0 removes the limit'). It distinguishes from sibling tools like qbittorrent_transfer_upload_limit (getter) and qbittorrent_transfer_set_download_limit by explicitly indicating upload and global scope.

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 conveys the core use case but does not explicitly mention alternative tools or prerequisites. There is no 'use this instead of X' guidance, so usage is implied by the name and description rather than clearly differentiated from per-torrent or download limit setters.

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