discord_delete_message

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

Annotations already declare destructiveHint=true, non-idempotent, and open-world. The description adds the critical 'Irreversible' warning and the permission nuance, both valuable. But with annotations carrying the safety profile, and the description adding only irreversibility and permissions, a 3 is appropriate – more detail on audit log or recoverability would raise it.

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 plus a return note. Every clause carries information: scope, permission, irreversibility, and sibling routing. Front-loaded and zero 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?

Output schema exists, so return values needn't be explained; the 'Returns: Confirmation' suffices. Description covers scope, permissions, and irreversibility. Missing only audit-log/reason behavior, which is minor given the schema documents 'reason'.

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 67%. The description doesn't mention any parameters by name; the schema documents channel_id, message_id, and reason. The description adds no parameter-level meaning, which is acceptable at baseline 3 when schema does substantial work, but it doesn't compensate for the remaining uncovered parameter.

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?

Specific verb+resource ('Delete one message') and explicitly distinguishes scope from the sibling discord_bulk_delete_messages by stating the bulk range (2-100). An agent can immediately tell this is the single-message deletion tool.

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?

Explicitly routes bulk operations to discord_bulk_delete_messages and notes the permission requirement (Manage Messages) for others' messages. Doesn't state when-not-to-use beyond the bulk case, but the context is clear.

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