roles_modify_positions

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

Annotations already indicate this is a mutating, non-destructive, idempotent operation. The description adds meaningful behavioral context: Discord renumbers other roles automatically and the tool returns the full role list after change. This goes beyond the annotation-provided safety profile without contradicting it.

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 well-structured with bold section headings (Purpose, When to use, Body, Returns) and contains no filler. Every sentence contributes to understanding the tool's action, usage context, request format, and return value, making it highly scannable and concise.

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 purpose, usage trigger, request body, and return shape, which is sufficient for tool selection and basic invocation. It does not detail permissions or rate limits, but given the moderate complexity and the presence of schema and annotations, these are not critical gaps.

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 100%, so the baseline is 3. The description's body note ('array of {id, position?}') largely mirrors the schema descriptions, which already explain that roles are auto-renumbered. The description adds minimal extra semantic value beyond what the schema provides.

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 'Bulk-reorder guild roles' via a specific PATCH endpoint. It uses a specific verb and resource, and the term 'bulk-reorder' distinguishes it from sibling tools like roles_modify, roles_create, and roles_delete. This is an unambiguous, well-differentiated purpose.

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 includes a 'When to use' section with an explicit example ('swap two adjacent roles') and clarifies it is for moving several roles in one transaction. However, it does not explicitly mention when not to use it or name alternative tools for single-role changes, so it lacks full exclusion guidance.

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