guild_begin_prune

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

Beyond the destructiveHint=true annotation, the description warns 'DESTRUCTIVE - kicked members must rejoin manually', explains timeout avoidance with compute_prune_count=false, and details the ConfirmRequired/__confirm/MCP_DRY_RUN security gate. This adds substantial behavioral context that annotations do not provide.

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 bolded sections and a front-loaded purpose, but the include_roles paragraph duplicates the schema description word-for-word, making it slightly less concise than it could be.

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 tool with 6 parameters, the description covers purpose, usage context, destructive consequences, role-pruning semantics, return shape, timeout behavior, and security gating. This is comprehensive enough for an agent to select and invoke the tool correctly.

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. The description largely restates the schema (especially include_roles, which is verbatim), but adds minor clarifications like compute_prune_count=false 'returns null' and that __confirm is gated by ConfirmRequired. This is not enough to meaningfully exceed the baseline.

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 opens with 'Kick inactive members', a specific verb+resource statement that clearly distinguishes this tool from siblings like members_kick (kicks a specific member) and guild_get_prune_count (previews the prune count).

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?

An explicit 'When to use' section states 'Reduce inactive bloat in large communities', giving clear context. However, it does not mention alternatives such as guild_get_prune_count for previewing the prune before committing, so it lacks full when-not-to-use guidance.

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