Reorder channels

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

Annotations indicate this is a non-read-only, non-destructive operation. The description adds behavioral nuance about relative positioning within channel groups and the optional parent category change, which goes beyond the annotations. It does not contradict 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 two sentences long, front-loaded with the primary action, and every word adds value. No fluff or redundancy.

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 is a mutating batch operation with a complex array parameter and no output schema. The description covers the core semantics and adds the important grouping rule, but it omits details like permission requirements or atomicity guarantees. Still, given the schema and annotations, it is reasonably complete.

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% for top-level parameters, so the description must compensate. It mentions 'positions' and 'parent category' but does not explicitly break down the array structure (channel_id, position, parent_id, lock_permissions). The schema itself provides some nested descriptions, but the description adds only partial semantic value, resulting in a 3.

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 action: 'Change the positions (and optionally the parent category) of multiple channels in one request.' This is a specific verb and resource, and it distinguishes itself from sibling tools like reorder_roles and create_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 provides clear context by noting 'in one request' and clarifying that positions are relative within channel groups. It implies this is for batch reordering, but it does not explicitly name alternatives or state when not to use this tool. Thus, it earns a 4.

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