discord_delete_message

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

Annotations are entirely absent, so the description carries the full burden of behavioral disclosure. It merely repeats the operation implied by the name and does not disclose that deletion is permanent/irreversible, what permissions are required (e.g., Manage Messages for other users' messages), or what the confirm parameter's default of false actually gates.

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 short and front-loaded, but the brevity is under-specification rather than genuine conciseness — a five-word sentence cannot adequately document a destructive operation with five parameters, a confirmation gate, and permission requirements.

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?

With an output schema present, return values need not be explained, but the description still leaves a destructive tool under-documented with no annotation support. The confirm-flag behavior, permission preconditions, and irreversible consequences are all missing, so an agent cannot safely or correctly invoke this tool based on the definition alone.

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%, and the description adds nothing about any of the five parameters. It does not explain what channel_id, message_id, guild_id, reason, or confirm mean, and the confirm flag (defaulting to false) is particularly underspecified for a destructive tool.

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 states a clear verb and resource: 'Delete a single message.' The word 'single' gives some implicit differentiation from sibling tools like discord_bulk_delete_messages and discord_purge_messages, but it does not explicitly name or contrast those alternatives.

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 no guidance on when to use this tool versus alternatives. With siblings like discord_bulk_delete_messages, discord_purge_messages, and discord_edit_message, an agent receives no explicit instructions about which tool fits which scenario, and no exclusions or prerequisites are mentioned.

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