Delete messages

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the write/destructive nature is covered structurally. The description adds real context beyond that: revoke=true scopes the deletion to everyone and is limited to '(your messages)'. It still leaves revoke=false behavior (delete-for-me-only) and irreversibility unstated.

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 tight sentences with no filler, and the core action plus the revoke switch are front-loaded. It is efficient, though the extreme terseness is part of why several parameter and behavioral gaps persist.

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 destructive, open-world tool with three parameters at 0% schema coverage and no output schema, the description is only partly sufficient. It never states that deletion is irreversible, what revoke=false does, or what identifier formats 'chat' accepts; annotations cover the safety hint but not these operational details.

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 description coverage is 0%, so the description must carry the load. It clarifies messageIds as message ids and gives semantics for revoke, but the 'chat' string parameter's accepted format (@username, numeric id, phone) is undocumented in both schema and description, and the default revoke=true is only implied.

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 gives a specific verb+resource ('Delete one or more messages in a chat by id'), which an agent can distinguish from siblings like telegram_clear_history, telegram_delete_chat, and telegram_delete_contacts. It does not, however, explicitly state how it differs from clear_history (bulk chat wipe) or delete_chat (whole-conversation removal).

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?

Usage is implied: target individual message ids rather than an entire chat. It gives no explicit when-to-use / when-not-to-use guidance versus the closely related telegram_clear_history or telegram_delete_chat, and states no prerequisites (e.g., needing to own the message or be an admin).

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