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

Annotations already indicate the operation is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false), which aligns with the description's 'move' action. The description adds useful context by noting it can handle 'one or more' items, but it does not disclose side effects such as ordering, atomicity, or what happens to the source group, which would enhance transparency.

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, concise sentence that immediately conveys the core functionality. There is no fluff or redundant content, making it highly efficient for the agent to parse.

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?

The tool has no output schema and only minimal annotations, so the description should carry more weight. It fails to mention return behavior, error conditions, or any effects on related data (e.g., whether items are removed from the source group or if order is preserved). The description is adequate for a simple read, but for a mutating operation with batch capability, it is under-specified.

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 schema description coverage at 0%, the description partially compensates by implying that 'jobs' refers to queue items and 'target_group_id' refers to the destination group. However, it does not specify the expected format for the 'jobs' string (e.g., comma-separated IDs, JSON array), leaving some ambiguity for the agent.

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 a specific action with a specific resource: 'Move one or more queue items to a different queue group.' It uses a distinct verb ('move') and indicates the target change (different queue group), effectively distinguishing it from sibling tools like reorder_queue_item or update_queue_item.

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 usage by stating the action and target ('to a different queue group'), but it does not explicitly mention when to use this tool versus alternatives, nor does it provide exclusions. There is no guidance on prerequisites or situations where this tool should be avoided.

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