discord_prune_members

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

The description states the action but does not disclose behavioral traits such as requiring confirmation (though hinted in the 'confirm' parameter's description), potential irreversibility, rate limits, or permission requirements. With no annotations, the description should provide more transparency about the destructive nature of the operation.

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 extremely concise at one sentence, which aligns with conciseness goals. However, it could be restructured to include key behavioral details without losing brevity.

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?

Given the tool's destructive nature (pruning members), the lack of output schema, and missing annotations, the description is inadequate. It does not explain default behavior (e.g., default days=7), what constitutes 'inactivity,' or how to preview the count (sibling 'discord_get_prune_count' exists but is not referenced).

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?

With only 25% schema description coverage, the description adds no meaning for parameters like 'days,' 'reason,' or 'guildId.' The sole parameter description exists in the schema for 'confirm.' The description fails to compensate for the low coverage, leaving most parameters unexplained.

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 uses a specific verb 'Prune (kick)' and identifies the resource as 'inactive members,' making the action clear. However, it does not distinguish itself from the sibling tool 'discord_kick_user' which also kicks members, missing an opportunity to clarify the difference between single vs. batch operations.

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?

No guidance is provided on when to use this tool versus alternatives like 'discord_kick_user' or 'discord_ban_user.' There is no mention of prerequisites such as required permissions or the context in which pruning is appropriate.

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