Delete Single Message from Chat

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds value by naming the exact environment prerequisites (TELEGRAM_SEND_ENABLED=true and TELEGRAM_DESTRUCTIVE_ENABLED=true), giving operational authorization context that is not present in the annotations. It does not contradict the annotations.

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 sentences with no fluff: the first states the primary action and mechanism, the second provides critical safety prerequisites. The main purpose is front-loaded, and every word earns its place.

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?

With an output schema present and a rich input schema covering all parameters, the description provides the essential missing context: destructive operation and environment-flag requirements. It does not explain post-deletion behavior or error cases, but the idempotentHint annotation and the output schema mitigate that need. Minor gap, but otherwise complete for the tool's complexity.

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%, with detailed descriptions for chat_id and message_id already present. The description only repeats 'by message ID,' which is already in the schema, so it adds no new parameter-level meaning beyond the baseline set by the schema.

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 opens with a specific verb and resource: 'Delete a single message from a chat by message ID.' It unambiguously distinguishes this tool from editing, pinning, or sending messages among the sibling tools, and the deletion scope (single message) is explicit.

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 gives clear operational context by stating the destructive nature and the two required environment flags, which tells an agent when its use is permitted. It does not explicitly name alternative tools or conditions where another sibling would be more appropriate, but no direct deletion sibling exists, so the context is sufficient.

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