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

Annotations already flag destructive and non-idempotent, and the description adds genuinely new behavioral facts: an admin permission requirement, that recent post/comment deletion is an optional cascade, and that the call defers to owner approval rather than completing immediately. That last point is the key operational surprise an agent needs, though it is not spelled out whether the call blocks or returns a pending status.

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?

Three short sentences, front-loaded with the action and side effect, with permissions and approval as follow-ups. Efficient overall; the approval sentence is slightly telegraphic given how much behavior it implies.

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 mutation with no output schema, the definition covers permission requirements, destruction scope, and the approval deferral, which are the main things an agent must anticipate. Gaps remain around the dependency between delete_recent_posts and member_id and around what a pending-approval response actually means.

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 schema already explains every parameter, including the member_id/membership_id split and the default for delete_recent_posts. The description only restates the post-deletion option at a high level and adds no format or interaction detail (e.g. that member_id becomes necessary when delete_recent_posts is set).

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 ('Ban a member from the group') with the optional side effect ('deleting their recent posts') made explicit. It is clear what the tool does, but it never distinguishes itself from the sibling `remove_member`, which an agent would also see in the list and could easily confuse with this one.

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?

'Admins only' gives one usage precondition, but there is no statement about when to choose ban over removal, no exclusions, and no indication of what happens when approval is refused. The boundary with `remove_member` is left entirely to inference.

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