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

Goes well beyond the annotations: states that omitted fields are preserved, that an empty buttons array removes buttons, and that channel ownership plus bot 'Edit messages' permission are required. These are the exact mutation semantics and authorization facts the destructiveHint/idempotentHint flags cannot convey.

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?

Four sentences, front-loaded with the action, then safety workflow, then mutation semantics, then scope exclusion. No filler or repetition of the title.

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, nested-schema mutation with no output schema, it covers what changes, what's preserved, permissions, and scope limits. It could note the retry semantics around request_id, though the schema description already handles that.

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 75%, so the schema already documents most parameters; the description still adds real meaning with the preserve-by-default rule for omitted fields and the empty-array removal semantics for buttons. Channel_id, request_id and confirmed are left entirely to their 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?

Names a specific verb ('Overwrite') plus the exact editable surfaces (text, caption, media, link buttons) scoped to 'one archived channel post'. The closing clause 'Not for comments or private chats' explicitly separates it from telegram_edit_message.

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 a clear precondition workflow ('Read it first and confirm the exact replacement and channel') and a negative boundary ('Not for comments or private chats'), which is what routes an agent away from the DM/comment edit sibling. It stops short of naming the alternative tool for those cases.

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