delete_message

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

Annotations already indicate destructive and non-read-only behavior, and the description adds the important context that the bot must have delete rights. While it does not discuss failure modes or irreversibility beyond the annotation, the permission requirement adds meaningful behavioral context.

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 two short sentences, with the core action front-loaded and the prerequisite immediately following. No waste, and the structure is highly scannable.

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 simple delete operation, the description covers the core action and the key precondition (delete rights). Annotations fill in the destructive nature. It omits return value or error handling, but with annotations and a straightforward use case, this is adequately complete.

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 schema provides a description for chat_id but not for message_id (50% coverage). The tool description does nothing to clarify parameter meanings or relationships, failing to compensate for the low schema coverage. Both parameters are left mostly implicit.

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 'Delete a message' uses a specific verb and resource, with the singular 'a message' clearly distinguishing it from the sibling tool 'delete_messages' (plural). The action is unambiguous and directly maps to the tool name.

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 clarifies when the tool is applicable by stating 'Bot must have delete rights in the chat,' which is a necessary prerequisite. However, it does not explicitly mention when to use the alternative 'delete_messages' for bulk deletion, leaving alternative-selection guidance implicit.

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