discord_delete_message

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

With no annotations, the description carries the full behavioral burden for a destructive, irreversible mutation, yet says nothing about permanence, required permissions (e.g. deleting another user's message), or what a successful response contains. The single word 'Delete' is the only signal, leaving the agent to infer the entire risk profile.

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?

One short, front-loaded sentence with zero wasted words. It is not padded, but the brevity here reads as under-specification rather than discipline — that gap is penalized in contextual completeness instead.

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 mutation with no annotations and no output schema, the description should disclose irreversibility, permission requirements, and the default-channel behavior. None of that is present, so an agent must guess at consequences before calling.

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%: both channel_id ('defaults to active') and required message_id are documented in the schema. The description adds no format or sourcing guidance (e.g. how to obtain message_id, or that channel_id can be omitted), so the 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 and resource ('Delete a message') with a scoping phrase ('from a channel'), which is enough to distinguish it from sibling write tools like discord_edit_message or discord_send_message, none of which delete. It falls short of 5 because it never clarifies whether the channel is resolved via channel_id or the active channel, nor whose messages can be deleted.

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 gives no when-to-use guidance, no prerequisites, and no alternatives — it does not mention discord_edit_message as the non-destructive option or discord_get_message_by_id for verifying the target before deletion. The only usage hint comes from the schema's 'defaults to active' note on channel_id.

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