Reorder channels

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

Annotations already indicate this is a non-read-only, non-destructive mutation. The description adds useful context about batching ('in one call') and optional category reassignment, but does not disclose further behavioral traits like permission requirements, atomicity, or how positions are interpreted relative to existing channels.

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 with no redundancy. It efficiently communicates the main action and key qualifier ('optionally into a different category').

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 description covers the core functionality (multiple moves, positions, category reassignment) and the schema and annotations provide supporting details. No output schema exists, but return values are not essential for this tool. Minor missing context like whether positions are absolute or relative, but this is a minor gap.

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 50%; the 'moves' parameter itself lacks a top-level description, but its items' fields (channel, category, position) are documented. The description's mention of moving channels to new positions and categories aligns with the schema but does not add deeper meaning beyond what is already in the input schema.

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 uses a specific verb ('Move') and resource ('channels'), and clearly states the scope: reordering positions and optionally moving to a different category. This distinguishes it from sibling tools like reorder_roles and update_channel.

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 ('Move channels to new positions... in one call') but does not explicitly contrast with alternatives such as update_channel or reorder_roles. It provides no exclusion criteria or when-not-to-use guidance.

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