qbittorrent_torrents_download_limit

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

The annotation readOnlyHint=true already covers safety. The description adds useful context about the input format (pipe-separated hashes or 'all') and units (bytes/s), which goes beyond the schema and annotations. This is meaningful behavioral disclosure.

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 sentence that conveys all essential information without fluff. It front-loads the core purpose and includes parameter details efficiently.

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 this simple read-only getter with an output schema, the description provides the necessary context: input format, unit, and keying. It does not need to explain return values because the output schema exists. It is complete for the tool's complexity.

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%, but the description fully explains the 'hashes' parameter: pipe-separated or 'all'. This directly compensates for the lack of schema documentation and is essential for correct usage.

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 resource and scope: per-torrent download speed limits in bytes/s, keyed by hash. It distinguishes from global transfer limits and setters, but lacks an explicit verb like 'get' or 'list', which slightly reduces 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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention that global limits are handled by qbittorrent_transfer_download_limit or that setting limits uses qbittorrent_torrents_set_download_limit. It only states what the tool returns.

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