qbittorrent_torrents_file_priority

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

Annotations already indicate it's not read-only and not destructive. The description adds context about ID format and priority levels but doesn't detail side effects like immediate application or reversibility. This is acceptable given the simple setter nature.

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?

Two concise sentences, front-loaded with the action, then clarifying parameters and values. No wasted words.

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 priority setter with an output schema, the description covers the essentials: action, ID source, and priority meanings. Missing explicit description of 'hash' could be a minor gap, but it's a common parameter across sibling tools.

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 0% schema description coverage, the description compensates by explaining 'id' as pipe-separated file IDs and defining priority numeric values. 'hash' is not described, but its purpose is likely inferable from the torrent context.

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 'Set file priority for a torrent' with a specific verb and resource. It distinguishes from siblings like increase/decrease priority by describing absolute priority values, and references the file contents tool for IDs.

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?

It explicitly instructs that file IDs come from qbittorrent_torrent_contents and explains valid priority values. Though it doesn't name alternatives, this context guides correct usage and disambiguates from related tools.

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