discord_purge_messages

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

No behavioral annotations are provided, so the description must carry the full burden. 'Purge' implies destructive behavior and the confirm note hints at a safety mechanism, but the description does not disclose irreversibility, required permissions, limits on what 'recent' means, or rate-limit/abuse considerations.

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 appropriately short and front-loaded, using two sentences with no filler. The phrase 'when enabled' is slightly ambiguous, but the overall structure is 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?

For a destructive tool with four parameters and no annotations, the description is incomplete. It lacks semantics for parameters, threshold of 'recent,' guild vs. channel targeting, and permission context. An agent would need to guess or rely on external guidance to call this safely.

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?

The schema provides no parameter descriptions and the description gives no additional meaning for amount, channel_id, guild_id, or reason. It only hints at confirm's role, leaving most parameters ambiguously specified.

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 ('Purge') and resource ('recent messages from a text channel'), making the core operation clear. It does not explicitly distinguish itself from the sibling discord_bulk_delete_messages, so it misses the top score.

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?

The description says what the tool does but never says when to use it instead of alternatives like discord_bulk_delete_messages or discord_delete_message. The only guidance is a vague confirmation requirement ('when enabled'), which is not enough to route an agent consistently.

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