Edit Discord Role

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

The description discloses that permissions replace existing values and returns updated role details. Annotations already indicate idempotence and non-destructiveness, and the description adds context about permission replacement. No contradictions with 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 well-structured: purpose first, then a helpful permission reference, then arg list. It is front-loaded but could be slightly more concise by reducing the permission list or integrating arg descriptions more succinctly.

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 7 parameters (2 required), no output schema, and good annotations, the description covers all parameters and notes the return type. It adequately informs usage for a mutation tool, though it lacks mention of error cases or validation behavior.

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 baseline is 3. The description adds value by listing common permission names, explaining color format with an example decimal, and providing permission examples. This goes 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 the tool edits a role's properties (name, color, permissions). The verb 'Edit' and resource 'role' are specific. However, it does not differentiate from sibling tools like discord_create_role or discord_edit_channel, though the name itself provides clarity.

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?

There is no guidance on when to use this tool vs alternatives such as discord_create_role or discord_set_role_positions. No prerequisites, context, or when-not-to-use information is provided, leaving the agent to infer usage.

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