Remove Discord role

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds only a minimal scope clarification that the role is removed from a member rather than deleted globally; it says nothing about permissions, the confirm parameter, audit-log reason behavior, or what happens if the member lacks 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?

The single sentence is front-loaded and free of waste, but it is under-specified rather than appropriately concise for a destructive five-parameter tool. The structure is clean but too thin to earn a higher score.

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 operation with five parameters, 0% schema coverage, and no annotation about permissions or confirmation, the description is substantially incomplete. The output schema reduces the need to describe return values, but the input-side and safety context remain largely absent.

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%, and the description names none of the five parameters. It implies that a member and a role are involved, but guildId, reason, and confirm are completely unexplained, and even the implied parameters lack naming or format detail.

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 states a specific verb and resource: remove a role from a guild member. This distinguishes it implicitly from discord_delete_role, which removes the role itself, but it does not explicitly name or contrast with sibling tools such as discord_assign_role.

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 versus discord_assign_role, discord_delete_role, or discord_update_role. The usage context is only implied by the verb 'Remove' and the phrase 'from a guild member.'

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