qbittorrent_transfer_info

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

The description adds context beyond the readOnlyHint by enumerating the specific data points returned (download/upload rates, totals, rate limits, DHT nodes, connection status). This sets expectations and is consistent with the annotation, with no contradictions.

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, front-loaded sentence that efficiently communicates the core purpose and key data fields. Every word adds value with no redundancy or fluff.

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?

Given the zero parameters, presence of an output schema, and readOnlyHint, the description is complete. It sufficiently defines the tool's scope without needing to explain return values, as the output schema covers that.

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 tool has zero parameters, so the description is not required to explain parameter meanings. The base score of 4 applies due to the absence of parameters, and the description rightly adds no parameter-specific 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 specifies the tool provides global transfer info including rates, totals, rate limits, DHT nodes, and connection status. This distinguishes it from sibling tools focused on transfer settings or per-torrent actions, despite lacking an explicit verb.

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 usage for retrieving global transfer statistics, but provides no explicit when-to-use or comparison with alternatives. With many sibling transfer tools, explicit differentiation would be valuable, but the content of the description makes the primary use case clear.

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