qbittorrent_torrents_upload_limit

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds minimal context by specifying the output is keyed by hash and that the input can be a pipe-separated list or 'all'. It does not disclose behaviors like missing hash handling or response details, but given the annotation, the bar is lower.

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 two sentences, front-loaded with the core purpose and immediately followed by the parameter format. Every word is necessary; there is no verbosity or irrelevant information.

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 simple read-only tool with one parameter and an output schema, the description covers the key aspects: what it returns, the unit (bytes/s), and how to specify torrents. It lacks an explicit verb and mention of the output structure, but the output schema likely provides that. Overall, it is sufficiently complete.

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%, so the description carries the full burden for parameter explanation. It clearly explains that 'hashes' is pipe-separated or the literal 'all', which is essential for correct invocation. It doesn't elaborate on what a hash represents or edge cases, but it addresses the main ambiguity.

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: per-torrent upload speed limits in bytes/s keyed by hash. It distinguishes from the global transfer level and the setter sibling (qbittorrent_torrents_set_upload_limit). However, it lacks an explicit verb like 'get' or 'list', so it's not a full 5.

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?

There is no explicit guidance on when to use this tool versus alternatives. The phrase 'Per-torrent' implies it is for individual torrents rather than global limits, but it does not directly state conditions or reference the global upload limit tool (qbittorrent_transfer_upload_limit) or the setter sibling.

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