members_remove_role

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

Annotations already declare idempotentHint=true, restrictiveHint=false, and readOnlyHint=false. The description adds the no-op behavior and return shape, but these are either implied by the idempotency hint or already covered by the output schema. No additional behavioral context like permissions or failure modes is provided.

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 well-structured with clear sections, bullet points, and no redundant sentences. It efficiently covers purpose, usage, exclusions, return value, and key behavior in a compact format.

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?

Given the simplicity of the tool, the annotations, and the full schema coverage, the description adequately covers purpose, selection guidance, and return behavior. It also points to the correct alternative for bulk role replacement, making the context complete for an agent.

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?

The input schema describes all 4 parameters with 100% coverage, so the baseline is 3. The description does not add new parameter-level meaning beyond what the schema already gives; it only clarifies that the operation removes a single role, which is evident from the name and schema.

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 and resource ('Remove a single role from a guild member') and clearly distinguishes from the sibling tool members_modify, which is for replacing the entire role set. It also implicitly contrasts with members_add_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?

Explicit 'When to use' and 'When NOT to use' sections are provided, including a concrete example (revoke @verified) and a named alternative tool (members_modify with roles). This gives the agent clear selection criteria.

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