deleteMessage

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses deletion limitations, the 48-hour window, specific exceptions for dice messages and creation service messages, permission requirements across chat types, and the success return value. This is far beyond the bare operation name.

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 long but every sentence adds necessary information about deletion constraints and permissions. It is front-loaded with the core action and the most important qualifier. It could be tightened with bullet points for readability, but there is no wasted content.

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?

Given a simple two-parameter tool with no annotations and no output schema, this description is unusually complete. It covers all essential edge cases: service messages, time limits, dice messages, bot permissions, channel/supergroup/group behavior, and the return value. An agent has enough information to know when the call will succeed or fail.

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 documents both parameters fully, including chat_id format and message_id meaning, with 100% schema description coverage. The description adds no extra parameter-level detail beyond what the schema provides, so the baseline score of 3 is appropriate.

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 begins with 'Delete a message' which is a specific verb and resource, and adds the key qualifier 'including service messages.' It clearly identifies the tool's function and is distinguishable from the sibling deleteMessages, which targets multiple messages.

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 rich context on when deletion is allowed, including time limits, message types, bot permissions, and chat types. However, it does not explicitly compare against the sibling deleteMessages tool or state when to prefer one over the other, so it lacks explicit alternative routing.

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