Delete a group or channel

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

Annotations already flag destructiveHint=true, but the description goes further by disclosing that deletion is permanent, that chat history is destroyed, that the chat ceases to exist for all members (not just this account), and that the operation is restricted to the creator. That permission constraint and irreversibility disclosure exceed what annotations provide.

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?

Three tight sentences: the destructive action first, then the sibling comparison, then the permission constraint. Every clause adds distinct decision-relevant information with no filler.

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 one-parameter destructive tool, the description covers irreversibility, scope of effect, and authorization. The only real gap is the missing format guidance for the 'chat' argument, which the bare schema does not fill in.

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?

Single parameter 'chat' with 0% schema description coverage, so the schema contributes nothing about accepted formats (username, numeric id, or invite link). The description never clarifies what the identifier should look like, leaving the one required parameter underspecified despite its simplicity.

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?

States a specific verb (delete), resource (group or channel), and scope (permanent, including history, for the account owner). It explicitly distinguishes itself from telegram_leave_chat and frames itself as the counterpart of telegram_create_group/telegram_create_channel, so an agent can pick it without opening other schemas.

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?

Gives explicit when/when-not routing: it names telegram_leave_chat as the weaker alternative for leaving only, and states the prerequisite that only the creator can delete ('Telegram refuses otherwise'). No inference required to choose between delete, leave, or create.

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