Delete messages

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

The description goes beyond the annotations by explicitly stating that deletion cannot be undone, that revoke affects all chat members, and that a confirm flag is required. This adds crucial behavioral details not present in the annotation flags (destructiveHint, idempotentHint).

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 concise, two sentences, with no redundant words. It front-loads the primary action and then explains key side effects and requirements.

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 destructive operation, the description provides sufficient context: what it does, irreversible nature, the revoke effect, and the confirm requirement. No output schema is needed given the simplicity.

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 already covers all parameters with clear descriptions (peer, message_ids, revoke, confirm). The description does not add additional parameter semantics beyond what is already provided, keeping the baseline at 3.

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 action ('Delete one or more messages') and the resource (messages). It distinguishes from siblings like 'edit' and 'send' by focusing on removal, which is unique among the listed tools.

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 provides context about the revoke option and the confirm requirement, implying when deletion is appropriate (e.g., permanent removal vs. local removal). However, it does not explicitly mention alternative tools or conditions for choosing delete over others, though none of the siblings directly compete.

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