discord_delete_role

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the bar is lower. The description adds concrete value beyond them by stating the blast radius (removed from every member) and the irreversibility/confirmation requirement, though it says nothing about audit-log reasoning or permission needs.

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?

Two short, front-loaded statements with no filler; the destruction scope leads and the caution follows. The trailing 'Returns: Confirmation.' is slightly redundant given an output schema exists.

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?

For a destructive mutation with annotations covering the safety profile and an output schema covering the return value, the description supplies the key missing behavioral context (scope + irreversibility). Only minor gaps remain, such as permission prerequisites.

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 67%, with 'reason' and 'guild_id' documented in the schema while 'role_id' is only implied by its name and pattern. The description adds no parameter syntax or format detail, so baseline 3 applies when the schema carries most of the load.

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+resource ('Delete a role') and clarifies scope ('removing it from every member'), which distinguishes it from edit_role, create_role, and set_member_role among the siblings.

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?

Provides a clear precondition: 'Irreversible — confirm with the user first,' which is actionable guidance for an agent. It does not, however, name alternatives (e.g., edit_role to modify rather than delete), so the routing guidance is incomplete.

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