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

Beyond annotations (destructiveHint, readOnlyHint=false), the description explicitly states 'Irreversible' and adds the permission prerequisite for deleting others' messages. It also discloses the batch execution capability. These are valuable behavioral details not present in annotations, though rate limits or error handling are not mentioned.

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—two short paragraphs—with the core purpose first, followed by key caveats and bulk support. Every sentence contributes meaningful information without redundancy.

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 deletion tool with destructive implications and bulk support, the description covers the essential aspects: the operation, irreversibility, permission requirements, and batch capability. It omits details like error behavior or rate limits, but these are not critical for invocation. Given no output schema, the description is reasonably complete.

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 0%, so the description must compensate. It does explain the bulk parameters (channel_ids, message_ids) and implies the single-item counterparts, but it does not clarify the 'account' parameter or how the single vs. bulk modes interact. Some parameter meaning is added, but partial coverage remains.

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 the verb 'Delete' and the resource 'message', and distinguishes from sibling tools like discord_edit_message and discord_send_message by specifying deletion. The mention of bulk support adds specific scope, making the purpose 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 description provides clear usage context: it states the permission requirement for deleting other users' messages (Manage Messages) and notes bulk support. It does not explicitly contrast with alternatives, but given the distinct operation, it is sufficient for an agent to know when to invoke it.

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