Discord Server Setup MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation operation ('reorders') but doesn't specify permissions required, whether changes are reversible, potential side effects on role hierarchy, or rate limits. This leaves significant gaps in understanding the tool's behavior.

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 extremely concise with two sentences that directly state the tool's function and parameter usage, with no wasted words. It is front-loaded and efficiently communicates the essential information.

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?

Given the complexity of a mutation tool with no annotations, no output schema, and incomplete parameter coverage (2 parameters with 0% schema description), the description is insufficient. It lacks details on permissions, effects, error handling, and doesn't fully explain all parameters, making it incomplete for safe and effective use.

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?

The description adds meaningful context beyond the input schema by explaining that the array should contain role IDs in 'desired order (highest to lowest)', which clarifies the semantics of the 'rolePositions' parameter. Since schema description coverage is 0%, this compensation is valuable, though it doesn't fully cover all parameters (e.g., 'guildId' is not mentioned).

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 verb ('reorders') and resource ('roles in the role hierarchy'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'edit_role' or 'create_role', which might also affect role properties, so it doesn't reach the highest score.

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 no guidance on when to use this tool versus alternatives like 'edit_role' or 'create_role', nor does it mention prerequisites such as needing a guild context. It only states what the tool does without contextual usage instructions.

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