Give or remove a role for many members (admin)

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds that results are reported per member, but says nothing about permission requirements, rate limits, partial-failure behavior, or how the two targeting modes interact if both are supplied.

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 short sentences, front-loaded with the action and resource before the targeting nuance; nothing wasted. Minor polish issues only (missing terminal period, slightly cramped phrasing of the second mode).

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, open-world bulk mutation with no output schema, the description should cover failure semantics and preconditions such as manage-roles permission. It covers the targeting model and per-member reporting but leaves those operational gaps for the agent to discover empirically.

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 60%, and the description compensates by explaining the relationship between user_ids and members_with_role ('or: everyone who has this role'), which the schema presents only as two parallel properties. It does not address which parameter wins if both are provided.

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 pair (add/remove) and resource (one role) plus both targeting modes, so the scope is unambiguous. It does not explicitly contrast itself with the sibling discord_admin_set_member_roles, so a reader must infer the bulk distinction from 'list of members'.

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 two usage modes — an explicit list of user IDs, or everyone currently holding another role — which is genuinely helpful selection guidance. It gives no when-not-to-use guidance and never names the alternative tool for single-member role changes.

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