discord_remove_role

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

With no annotations, the description carries the full burden of disclosure. It exposes one meaningful behavior: it respects Discord's role hierarchy. However, it does not mention required permissions, how failures are surfaced, or what happens if the member already 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 description is one compact sentence with no filler. It front-loads the core operation and includes the key hierarchy caveat in second place, making it easy for an agent to scan.

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 mutation tool with no annotations, this is borderline adequate but incomplete. It covers the main operation and one constraint, but omits contextual details like the required permissions, conflict with hierarchy, and expected behavior on invalid input. The presence of an output schema reduces some burden, but the description still leaves too much implied.

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%, so the description must compensate for parameter meaning. It implies that role_id and member_id are important, but it says nothing about the optional reason parameter, guild_id behavior, or how the guild is determined. The names are somewhat self-explanatory, but the description adds no real parameter-level guidance.

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 ('Remove') with a clear resource and target ('a role from a member'), making the operation unambiguous. It also differentiates from siblings like discord_delete_role and discord_assign_role without needing to open the schema.

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 implies the obvious use case—when a member should stop having a particular role—but does not explicitly contrast it with discord_assign_role or mention any prerequisites, such as hierarchy position or permissions. The hierarchy phrase is a hint at constraints, not an explicit routing or exclusion rule.

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