set_priority

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

No annotations provided, so the description carries the burden. It explains the effect of each priority value, but lacks details on whether the change applies immediately, affects running transfers, or has side effects. More depth would be helpful.

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?

A single, efficient sentence that conveys the purpose and the allowed values. No unnecessary 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 mutation tool, the description covers the basic intent. However, it doesn't mention that multiple hashes can be set at once or the behavior when priority changes while a transfer is active. Output schema is absent, but the return value is likely minimal.

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?

Schema coverage is 0%. The description clarifies the 'priority' enum values, especially that 'off' means 'do not transfer'. However, it does not explain the 'hashes' parameter (e.g., how to obtain hashes). The compensation is partial.

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 explicitly states the action 'set torrent bandwidth priority' and lists the four possible values with an explanation for 'off'. This clearly distinguishes it from sibling tools like add_torrent, remove_torrent, etc.

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 this tool: when you want to set bandwidth priority. It does not explicitly state when not to use or mention alternatives, but the context is clear given the sibling tools.

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