discord_delete_dm

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

The description adds value beyond annotations by emphasizing irreversibility ('IRREVERSIBLE'), scoping to bot's own messages, and noting the return of a confirmation. Annotations already state destructiveHint=true, so this is consistent and provides extra context.

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 two sentences, front-loaded with the core action and key constraints. Every sentence is informative and there is no wasted text.

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?

The description is fully complete for this tool's complexity: it covers the action, scope, constraints, and return value ('Returns a confirmation'). No output schema is needed as the confirmation message is self-explanatory.

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?

The input schema provides clear descriptions for both parameters, and the description adds critical context: the message must be previously sent by the bot. This supplements the schema's coverage (100%) and helps the agent understand the constraint.

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 tool's action ('permanently delete'), the specific resource ('DM message'), and the constraint that it only applies to the bot's own messages. This distinguishes it from sibling tools like discord_delete_message which targets channel messages.

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 implicitly indicates usage (for bot's own DM messages) but does not explicitly state when not to use it or provide alternatives. It assumes the agent can infer from the name and context, but explicit guidance would be beneficial given the sibling list.

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