discord_mod_purge_messages

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

With no annotations provided, the description carries full burden. It mentions 'scans and bulk-deletes', indicating destructive behavior, but lacks details on permissions required (e.g., 'manage messages'), irreversibility, rate limits, or error handling (e.g., bot permission checks).

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?

Single sentence that front-loads the main action. However, it could be more structured (e.g., listing filters explicitly). Overall concise with no wasted words.

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?

Missing crucial context for a destructive 7-param tool: no explanation of return values (e.g., count of deleted messages), error conditions (e.g., missing permissions, message too old), or behavior limitations (e.g., cannot delete messages older than 14 days). Minimal for its complexity.

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 100%, so all parameters are documented. The description adds context by mentioning filters (by user, content, attachments) that map to authorId, contains, hasAttachment, but this is partially redundant with schema descriptions. Baseline 3 is appropriate.

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 'Purges messages from a channel with filters' – a specific verb (purge) and resource (messages). It distinguishes from sibling tools like discord_mod_bulk_delete_messages by emphasizing filtering capabilities (by user, content, attachments).

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 on when to use this tool versus alternatives like discord_mod_bulk_delete_messages. The description does not specify prerequisites, permissions, or exclusive contexts (e.g., 'use when you need filtered deletion').

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