queue_move_up

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

Annotation Contradiction: idempotentHint=true conflicts with the description's 'one place up' semantics, since calling it twice moves a torrent from position n to n-2, not the same as one call. No additional behavior (e.g., effect when already at top, or ordering of multiple ids) is disclosed.

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, front-loaded sentences; the action is stated first and the parameter note is separated into a simple Args block. No filler or redundant schema repetition.

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?

With an output schema present and only one required parameter, the mechanics are mostly covered. However, the idempotency contradiction and lack of edge-case guidance make it incomplete for safe repeated use.

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%, but the description compensates by stating 'ids: Torrent ids or hash strings,' clarifying the accepted parameter beyond the generic anyOf array/string/integer. It does not detail how multiple ids are ordered, but for a one-param tool this is adequate.

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?

States a precise verb and resource: 'Move torrents one place up the queue.' The qualifier 'one place up' distinguishes it from queue_move_top, queue_move_down, and queue_move_bottom without needing those schemas.

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 explicit when-to-use or alternative routing is given. The operation is clear enough to infer it is for one-step queue promotion, but it does not mention queue_move_top for 'send to top' or how to choose among the four queue commands.

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