Delete a message

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

Annotations already state destructiveHint=true and readOnlyHint=false. The description goes beyond this by emphasizing irreversibility ('This cannot be undone') and requiring user confirmation, which is meaningful added context. It also narrows the operation to messages the authenticated account sent.

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 convey the action, the restriction, the irreversibility, and the required user confirmation without any wasted words. The most important caveat is front-loaded.

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 simple one-parameter tool with a full input schema, an output schema, and annotations covering destructiveness, the description provides all needed operational context: what is deleted, who can delete it, and what to do before invoking.

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 schema already covers the single parameter with 100% description coverage, so the description need not add much. It does reinforce that the message must be a directly sent message, but it adds no additional details about message_id beyond the schema.

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 uses a specific verb ('Delete') and a precise resource ('a single direct message the authenticated account sent'), clearly distinguishing it from deleting an entire conversation or sending a message. The scope is 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 clearly indicates this is for single direct messages and only for messages sent by the authenticated account, which is essential context. It also instructs the agent to confirm with the user before calling, but it does not explicitly name sibling alternatives like repovive_delete_conversation.

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