qbittorrent_transfer_toggle_speed_limits

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

Annotations already flag this as a mutating action (readOnlyHint false) and non-destructive (destructiveHint false). The description adds the specific toggle behavior, which is exactly what the tool does. While it doesn't mention side effects or permissions, the simplicity of the action and the annotation coverage make this sufficient.

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: 'Toggle the alternative speed limits on/off.' It is maximally concise, contains no redundant information, and every word contributes to the meaning.

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?

This is a trivial tool with no parameters and an output schema provided. The description covers the only behavioral aspect (toggling) fully. There is no need to explain return values because the output schema exists, and the low complexity means nothing else is required for the agent to invoke it 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?

With zero parameters, the input schema is fully covered and there is nothing to explain. The description correctly avoids adding false parameter details. Baseline for 0 params is 4, as the description cannot add parameter-specific value beyond what the empty schema communicates.

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 uses a specific verb 'Toggle' and clearly identifies the resource ('alternative speed limits') and the action (on/off). It distinguishes itself from sibling tools like qbittorrent_transfer_speed_limits_mode (which reads the mode) by intentionally flipping the state, so the purpose is unambiguous.

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 the use case—when you want to switch between normal and alternative speed limits—but does not explicitly state when to use it versus reading the current mode (qbittorrent_transfer_speed_limits_mode) or setting specific limits. There are no exclusions or alternative tool mentions, so it falls short of clear contextual guidance.

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