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

The annotations indicate a state-changing operation (readOnlyHint=false) but provide no safety profile. The description adds almost no behavioral context: it does not mention effects on other queue items, reversibility, or the meaning of the optional 'from' parameter. With minimal annotation support, the description carries the burden of transparency and falls short.

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 a single, front-loaded sentence that conveys the core operation without any filler. It is appropriately sized and every word earns its place.

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?

Given the three parameters, no output schema, and the presence of similar sibling tools (move_queue_item, reorder_queue_group), the description is incomplete. It does not clarify scope within a queue, the role of 'from', or how this differs from moving an item to another queue. The lack of such context makes it difficult to select correctly among siblings.

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 description coverage is 0%, so the description must compensate. It clarifies that queue_item_id identifies the item and that 'to' is the 1-based position, but it completely ignores the optional 'from' parameter, leaving its purpose unexplained. This is a significant gap for a reorder operation.

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 the verb 'move' and the resource 'queue item', and specifies the positional scope ('to a new 1-based position'). It distinguishes from group-level tools like reorder_queue_group by saying 'single', but it does not explicitly differentiate from the similarly named sibling move_queue_item, so it is not fully distinguished.

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 need to reorder a single queue item), but it provides no explicit guidance about alternatives or exclusions. There is no mention of when not to use it or how it relates to move_queue_item, reorder_queue_group, or update_queue_item.

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