discord_delete_role

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

No annotations are provided, so the description carries the full burden. It discloses the MANAGE_ROLES requirement, but says nothing about irreversibility, that the role is stripped from all members holding it, whether managed/@everyone/default roles are protected, or what the response contains. For a destructive operation this leaves the most important behavioral traits undisclosed.

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 with the destructive action first and the permission requirement immediately after; zero filler and nothing buried.

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?

A destructive administrative tool with no annotations and no output schema should at minimum state irreversibility and blast radius. The description covers only the permission gate, leaving an agent unable to judge consequences before calling it.

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 100%, so both role_id and guild_id are documented in the schema, including the 'defaults to active server' behavior for guild_id. The description adds nothing beyond the schema, which is the expected baseline here.

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 role from a server'), which is clear and distinguishable from create_role and modify_role by name. It does not explicitly contrast with discord_remove_role, which removes a role from a member rather than deleting the role object — the nearest source of confusion among 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?

The parenthetical gives a real prerequisite (MANAGE_ROLES), which is genuine usage context. However, it gives no guidance on when to delete vs. modify a role, and no warning that deletion is not the same as remove_role/assign_role, nor any exclusions or preconditions such as ownership or managed-role restrictions.

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