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

Annotations already declare destructive=true, idempotent=true and openWorld; the description adds real value beyond that by spelling out the privilege model (owner-only for moderator removal) and both accepted auth paths (Bearer header or key argument). It adds a security caveat about key retention in client history, though it does not say what a failed removal leaves behind or whether the action is reversible.

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?

Purpose and privilege rule are front-loaded, which is good, but the one-sentence chain is dense and the key-retention warning is repeated verbatim from the key parameter's schema description, which is duplicated effort rather than added 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 destructive, open-world mutation with no output schema, the definition covers access rights, auth methods, and idempotency (via request_id in schema). It stops short of describing error/permission-failure behavior or the reversibility of a removal.

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%. The description restates account_id ("the target member's account_id") and repeats the key-auth guidance already in the key schema description, adding little. The undocumented community_id is left unexplained in both places, so the baseline 3 is appropriate.

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?

Names a specific verb and resource ("Remove an ordinary member from a private community") and immediately scopes it with the role rule "only the owner can remove a moderator". An agent can distinguish this from community_member_role, community_leave, and community_invite_revoke without opening 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?

States the conditions for use: owner or moderator access, account scope, and that the target must be an ordinary member (moderators require owner). It does not explicitly name sibling alternatives such as community_leave or community_member_role, but the who-can-do-what rule is clear enough to select correctly.

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