qbittorrent_transfer_download_limit

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

The readOnlyHint annotation already indicates a read-only operation. The description adds value by specifying the unit (bytes/s) and the meaning of zero (no limit), which helps the agent interpret the returned value correctly. No contradiction with annotations.

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, informative sentence conveys all necessary information without any redundancy. It is front-loaded with the core purpose and includes the key detail about the zero value.

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 getter with no parameters, the description is complete. It conveys the return value's unit and semantics, and the readOnlyHint annotation covers safety. No additional context is needed for an agent to use this 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 has zero parameters, so there is nothing to document. The baseline for zero parameters is 4, and the description appropriately provides no redundant parameter information.

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 that the tool retrieves the global download speed limit in bytes/s, with 0 indicating no limit. This specific verb and resource scope distinguish it from per-torrent limits and the setter tool (qbittorrent_transfer_set_download_limit).

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 implies its usage through the word 'Global' but does not explicitly mention when to use this over related tools (e.g., per-torrent download limit) or provide exclusions. No alternatives are named, so the guidance is minimal.

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