discord_edit_role

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

Annotations (readOnlyHint: false, destructiveHint: false, idempotentHint: true) indicate a safe, idempotent mutation. The description adds permission and hierarchy constraints not captured in annotations, and clarifies that permissions are replaced if provided. 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?

Three sentences: first covers purpose, second clarifies update behavior, third adds prerequisites. No redundant information. The most important information (what the tool does) is front-loaded.

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 tool has 7 parameters, no output schema, and annotations signal open-world, the description covers partial update behavior, permissions replacement, and critical preconditions. It does not mention return value or common errors, but for an edit tool these are less essential. Overall adequate for correct invocation.

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% with descriptions for each parameter. The description adds value by stating 'Only provided fields change,' which is a general behavior not repeated in any single parameter description. For permissions, it reiterates the replacement behavior already in the schema, but the partial update context is an important addition.

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 starts with 'Update an existing role's name, color, permissions, hoist, or mentionable flag.' It clearly states the verb (update) and resource (existing role). This differentiates from create_role (create), delete_role (delete), and set_role_permission (permissions-only update).

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 usage context: 'Only provided fields change' and 'passing permissions REPLACES the role's full permission set.' It also specifies preconditions: 'Requires the Manage Roles permission, and the role must be below the bot's highest role.' It does not explicitly name alternative tools like discord_set_role_permission, but the permissions replacement hint implies when to use this vs. a single-permission tool.

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