Prune members

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

Description reveals the two-phase behavior (preview then destructive) beyond annotation 'destructiveHint=true'. It explains the confirmation token mechanism and that the first call is safe.

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?

Two sentences with no fluff. First sentence states purpose, second explains critical usage detail. Front-loaded and efficient.

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?

Covers core workflow and safety. Lacks explicit return value details for the first call, but says it returns a confirm_token. Given no output schema, description is sufficiently complete for a destructive prune tool.

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 40%; description implicitly explains confirm_token and dry_run by describing the two-step flow, but does not detail guild or reason. Adds some meaning beyond schema but not enough for full clarity.

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?

Description clearly states the tool removes members inactive for a number of days who hold no roles. This specific verb+resource+conditions distinguishes it from sibling tools like ban_member, kick_member, etc.

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?

Describes two-step usage: first call previews, second call with confirm_token executes. Explicitly says 'Safe to call directly', but does not contrast with alternative tools for similar operations.

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