queue_move_top

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

Annotations already establish that this is a non-read-only, idempotent, non-destructive operation. The description adds context by framing the action as a queue reordering, but it discloses little beyond that. There is no contradiction with the annotations.

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 very short, front-loaded, and contains no filler. The one-sentence action plus a single Args line is appropriately sized for such a simple tool, though it could have used one sentence to mention the queue_move_up sibling.

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 one-parameter tool with an output schema and annotations, the description is nearly complete for making a correct call. The main gap is not explaining how this tool differs from queue_move_up, but that affects tool selection rather than invocation correctness.

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 schema only names the parameter 'Ids' with no description coverage, so the description's clarification that ids can be torrent IDs or hash strings is valuable. It meaningfully explains what kind of values to pass, even without examples or multi-value syntax.

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 says the tool moves torrents to the front of the queue, giving a specific verb, resource, and destination. It is understandable on its own, though it does not explicitly distinguish itself from sibling tools like queue_move_up or queue_move_bottom.

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 gives no guidance on when to use this tool versus the closely related queue_move_up, queue_move_down, or queue_move_bottom tools. The intended action is implied by 'front of the queue,' but no exclusions or alternative routing are provided.

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