discord_reorder_rolesSet role positions in a Discord guild to reorder the role hierarchy and adjust permission ordering.
Set role positions within a guild.
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | ||
| confirm | No | ||
| guildId | Yes | ||
| positions | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| name | No | ||
| error | No | ||
| action | Yes | ||
| roleId | No | ||
| userId | No | ||
| guildId | No | ||
| updated | No | ||
| positions | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already disclose destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say that positions are replaced wholesale, that role hierarchy constraints apply, or that a confirm flag must be supplied before a destructive reorder.
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?
A single short sentence with zero waste and the resource front-loaded, but the brevity comes from under-specification rather than disciplined editing. Nothing about the destructive semantics earns a place because nothing is said.
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?
An output schema exists, so return values need not be described. However, for a destructive mutation tool with a confirm parameter and zero schema coverage, the description leaves the agent without the operational detail needed to call it safely.
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% across 4 parameters, and the description supplies no meaning for any of them. The nested positions array (roleId/position pairs), the optional reason audit string, and the confirm safety flag are all completely undocumented in prose.
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?
States a specific verb and resource ("Set role positions within a guild"), which distinguishes it from discord_update_role (editing role attributes) and discord_reorder_channels (channels, not roles). It is clear, but does not explicitly name the siblings it differs from.
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?
No guidance on when to use this versus discord_update_role or discord_reorder_channels, no prerequisites (Manage Roles permission, role hierarchy limits), and no mention of the confirm gate implied by the schema. The agent must infer everything about invocation context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
This server cannot be deployed