qbittorrent_transfer_upload_limit

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

The annotation readOnlyHint=true already signals a safe read operation. The description adds valuable behavioral context by stating the sentinel value '0 if no limit is applied' and the unit 'bytes/s', which goes beyond the annotation.

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 concise sentence that conveys all essential information without any filler. It is front-loaded with the core concept and immediately provides units and edge-case 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 parameterless getter, the description is nearly complete. It defines the meaning of the return value and the zero case. The presence of an output schema (though unspecified) reduces the need to detail the return format. It could have explicitly stated this is a read-only retrieval, but the overall context is sufficient.

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 parameter semantics are trivially satisfied. The description doesn't need to explain parameters, and the baseline of 4 is appropriate given the absence of parameters.

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 as the global upload speed limit and specifies units (bytes/s). However, it lacks an explicit verb like 'get' or 'retrieve', making it a noun phrase rather than an action statement. It still distinguishes from sibling tools like the download limit and set_upload_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?

No guidance is provided on when to use this tool versus alternatives. While siblings like set_upload_limit imply this is a read operation, the description does not explicitly state its role or contrast with related tools.

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