Bulk delete up to 100 recent Discord messages in a channel. Messages must be under 14 days old; optional audit reason provided.
Bulk delete (purge) multiple recent messages in a channel (max 100, messages must be < 14 days old)
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | Number of messages to delete (2-100) | |
| reason | No | Audit log reason | |
| channelId | Yes | Discord channel ID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries the full burden. It usefully discloses the 14-day age limit (not present in the schema) and the 100-message cap, which are real behavioral constraints, but it omits permission requirements (Manage Messages), irreversibility, and partial-failure behavior.
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?
A single front-loaded sentence with the core action first and the two hard constraints parenthesized. No waste.
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, annotation-free mutation tool with no output schema, the definition covers the practical constraints but leaves out permissions, irreversibility, and what happens when messages exceed 14 days. Adequate but with clear gaps.
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 all three params are already documented. The description restates the max-100 constraint already in the schema and adds no syntax or format detail for 'reason' or 'channelId'. Baseline 3 applies.
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?
States a specific verb+resource ('Bulk delete (purge) multiple recent messages in a channel') and the 'bulk/multiple' scope implicitly distinguishes it from the singular delete_message sibling. No sibling is named explicitly, so it stops short of full differentiation.
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 constraints (max 100, <14 days old) imply when it is applicable, but there is no explicit when-to-use/how-it-differs-from-delete_message guidance. Usage is inferable rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.