⚠️ Delete message

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

Warns that deletion is 'IRREVERSIBLE' and 'visible to the other party (a 'deleted' marker remains).' Discloses behavioral traits beyond annotations: dry run preview, idempotency key behavior. No contradiction with annotations (destructiveHint=true is consistent).

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 4 sentences but includes action, warnings, prerequisites, and user confirmation requirement. It is front-loaded with the core purpose and wastes no words.

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?

Covers all critical aspects: irreversibility, visibility, ownership constraints, required IDs and their sources, dry run, idempotency, and confirmation. No output schema exists, but return behavior is not needed. Complete for a destructive operation.

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 100%, and the description adds meaning: source of chat_id and message_id, explanation of dryRun as a safe preview, and idempotencyKey for duplicate protection. This goes beyond the schema descriptions.

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 explicitly states 'Deletes a SINGLE message from a chat by message_id.' It uses a specific verb and resource, clearly distinguishing it from sibling messenger tools like send, read, or get.

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?

Provides explicit when-to-use guidance: 'You can usually delete only your own messages.' Advises confirming with the user before calling and specifies required IDs and their sources ('chat_id and message_id (from messenger_get_messages_v3)').

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