discord_prune_members

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

Adds context beyond annotations: 'Removal is irreversible (members must rejoin)' aligns with destructiveHint=true, 'SAFE BY DEFAULT' mitigates risk, and 'Requires the Kick Members permission' details authorization needs. No contradiction with annotations.

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?

Very concise: two sentences covering purpose and safety, plus one sentence on irreversibility and permission. Every sentence earns its place, no fluff.

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 safety, irreversibility, and permission. The dry_run behavior is explained in the narrative. However, it does not describe the return value of dry_run (count of members) which is in the schema but might be missed. Still quite complete.

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 baseline is 3. The description adds value by explaining the dry_run parameter's behavior in the narrative, but does not provide extra details on other parameters beyond the schema.

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 clearly states 'Remove members who have been inactive (no roles, not seen) for a number of days.' It specifies the verb 'remove', the resource 'members', and the condition 'inactive', distinguishing it from sibling tools like discord_kick_member or discord_ban_member.

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?

Provides explicit guidance: 'SAFE BY DEFAULT: dry_run is true... so call it first to preview the count, then re-call with dry_run:false to actually remove them.' It also warns about irreversibility and required permission, giving clear when-to-use instructions.

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