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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds substantial non-structured context: authorization tiers, the last-Owner refusal, immediate session termination, and the fact that keys the member minted keep working. That is exactly the side-effect detail an agent needs before a destructive call.

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 critical fact (what is removed, and that it is destructive) is front-loaded, and the later clauses each carry a distinct permission or side-effect detail. It is dense and semicolon-chained, which slightly hurts readability, but no sentence is padding.

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?

With only two fully documented parameters, no output schema, and annotations covering the safety profile, the description closes every remaining gap: authorization, refusal conditions, post-removal effects, and the confirmation workflow. An agent has everything needed to invoke it correctly and safely.

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 100%, so the baseline is 3, but the description adds real meaning by framing confirm as a two-step social gate (ask the person, then set confirm: true only on agreement) rather than a bare boolean. It also ties memberId to list_members output, reinforcing the schema note.

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 and resource ('Removes a member from the organization') and immediately extends the scope to the second case it covers ('or revokes a pending invitation'). This is enough for an agent to separate it from invite_member, resend_invitation, and revoke_project_grant without opening any 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?

Supplies concrete prerequisites (needs Owner or Admin, removing an Owner needs an Owner, last Owner is refused) and an explicit call protocol: call without confirm first, then pass confirm: true only if the person agrees. It does not name an alternative sibling tool for borderline cases, so it stops short of a 5.

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