Remove role

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds behavioral context by stating it 'preflights the bot's role hierarchy so a failure is an explanation, not a 403,' which discloses a meaningful implementation detail that affects error handling.

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 sentences, front-loaded with the primary action and a concise behavioral note. Every word earns its place with no redundant information.

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 straightforward role-removal tool with clear schema coverage and annotations, the description is sufficient. It covers the core function and an important behavioral detail; no output schema exists, so return values don't need explanation.

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 75% with descriptions for role, guild, and member; the description itself does not elaborate on parameter usage. The schema already explains names/IDs, and reason is self-explanatory, so the description adds no extra meaning but doesn't need to compensate significantly.

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 uses a specific verb+resource: 'Take a role away from a member.' This clearly distinguishes it from sibling tools like assign_role (giving a role) and delete_role (deleting the role entirely).

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 clearly implies when to use this tool—whenever a role needs to be removed from a member—but does not explicitly name alternatives or exclusions. The preflight note adds context about error handling, which helps the agent understand expected behavior.

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