Delete Discord role

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotency, so the safety profile is covered structurally. The description adds the important behavioral precondition of confirmation and backup acknowledgement, but it does not explain irreversibility, permission requirements, or what deletion does to members holding the role.

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 front-loaded sentence that identifies the action and its preconditions without filler. Every phrase contributes to the operation.

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?

This is a destructive, six-parameter operation with no schema descriptions, so the description should do more. It omits required parameter meaning, the irreversible consequences of role deletion, and how confirmation/backup acknowledgement are supplied, leaving major gaps for an agent.

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% for six parameters, so the description must compensate and largely fails to do so. It vaguely gestures at 'confirmation' and 'backup acknowledgement' but gives no meaning for guildId, roleId, reason, confirm, backupId, or allowWithoutBackup.

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 ('Delete a Discord role'), which clearly separates it from siblings like discord_update_role or discord_remove_role. The added precondition phrase does not obscure the core action.

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 phrase 'after confirmation and backup acknowledgement' implies prerequisites for use, which is useful context. However, it does not state when to choose deletion over alternatives such as updating or reassigning a role, nor what happens if the preconditions are not met.

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