Bulk delete Discord messages

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

Annotations already declare destructiveHint=true, non-idempotent, open-world, so the safety profile is covered. The description adds that a confirmation and backup acknowledgement are needed, which is genuine extra context, but it never explains the escape hatch (allowWithoutBackup), what happens if confirmation is omitted, or whether deletion is recoverable after a backup.

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?

Two short sentences, front-loaded with the action and mode selection, followed by the gating requirements. No filler.

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?

An output schema exists so return values need no explanation, but with 7 parameters at 0% schema coverage the description should clarify the confirm/backupId/allowWithoutBackup workflow and how to obtain a backupId. Those gaps are material for a destructive operation.

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 0%, so the description must carry the load; it loosely maps to limit, messageIds, confirm and backupId/allowWithoutBackup, but leaves 'reason' and the required channelId unexplained and does not clarify that the two deletion modes are mutually exclusive. Partial compensation only.

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 and resource ('bulk delete messages') and distinguishes the two operating modes (by count or explicit message IDs), which separates it from the read-only sibling discord_list_channel_messages. It does not name a concrete alternative tool, but the action is unambiguous.

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 sentence 'Requires confirmation and backup acknowledgement' implies prerequisites but never states when to prefer count-based deletion over explicit IDs, nor when a backup must exist first. Usage conditions are implied rather than spelled out.

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