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

Goes well beyond the annotations: posts are retained, the removed member retains the ability to re-ask to join, unban is non-destructive in the same call, admin privilege is required, per-call confirmation is on by default and toggleable, and the call may block on owner approval. These are exactly the behavioral traits an agent needs before invoking a destructive tool.

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?

Front-loads the purpose well, but the body is telegraphic and partially redundant ('as Membership settings, Remove does', 'as Unban does'), and the fragment 'Admins and moderators.' has no clear referent. Tightening the authority and confirmation statements into full clauses would remove ambiguity without losing content.

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, approval-gated mutation with no output schema, the description covers who can call it, what is destroyed and what survives, reversibility (rejoin request), and the approval flow. The only gap is what happens to non-post content (comments, messages) and the shape of the response, plus the ambiguous authority fragment.

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?

Both parameters are fully documented in the schema ('group' URL name, 'membership_id' from list_members), so the schema carries the burden. The description adds no format, sourcing, or constraint detail beyond it. Baseline 3 is appropriate at 100% coverage.

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 specific verbs and resource: 'Remove a member from the group, or lift a ban.' It maps the behavior to the equivalent UI actions (Membership settings > Remove, Unban), which is genuinely clarifying. It does not explicitly name ban_member as the alternative for the opposite action, so sibling differentiation is only implicit.

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?

Gives real operational context: 'Admins only', confirmation is on by default but can be switched off for this tool, and the call waits for the owner's approval. It clarifies the dual use case (remove vs. unban on a banned member) rather than leaving the agent to guess. It stops short of naming a sibling to reach for instead, e.g. ban_member.

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