qbittorrent_torrents_top_priority

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

The description adds behavioral context beyond the annotations by explicitly stating the mutation is a queue reordering to the top. Annotations already indicate readOnlyHint=false and destructiveHint=false, and the description is consistent with those, providing the specific effect without contradiction.

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 long with no filler. The first sentence states the primary action, and the second provides necessary parameter details. Every word earns its place, and the key information is front-loaded.

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 tool with one parameter and a clear effect, the description covers the action and parameter semantics completely. The existence of an output schema means return values don't need to be explained, so no gaps remain.

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 only defines 'hashes' as a string with no description (0% coverage). The description compensates fully by stating 'pipe-separated or "all"', giving both the format and a special accepted value, which is essential for correct invocation.

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 the specific verb 'Move' with resource 'torrents' and destination 'top of the queue', making the action unambiguous. It clearly differentiates from siblings like 'increase_priority' or 'bottom_priority' by specifying the exact queue position.

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 when to use the tool (when you want to move torrents to the top of the queue) but does not explicitly mention alternatives or when not to use it. There is no exclusionary guidance, but the action is self-explanatory enough for a straightforward priority operation.

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