message_delete

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

The description merely restates the tool name ('Delete a message') without adding any behavioral context. With no annotations, the burden is on the description to disclose effects like permanent deletion, admin/everyone behavior, or media removal—none are mentioned.

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 extremely short, but it is under-specified rather than concise. It lacks front-loaded essential details for a 5-parameter mutation tool, making it closer to a placeholder than an informative summary.

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?

The tool's complexity (5 params including everyone and clearMedia) demands more context. The good schema covers parameters, but the description provides no operational context, such as what happens to media, whether deletion is reversible, or when to set 'everyone'.

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 description coverage is 100% for all 5 parameters, so baseline is 3. The description adds no additional parameter meaning beyond the schema, but the schema already documents each field well (e.g., 'everyone' for global deletion, 'clearMedia' for media removal).

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 states the action clearly: 'Delete a message from the chat'—a specific verb and resource. It distinguishes from sibling tools like chat_delete (deleting the entire chat) and message_edit, though it lacks nuance about deletion scope (everyone vs. self).

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?

No guidance is provided on when to use this tool versus alternatives such as chat_clearMessages (clearing all chat messages) or chat_delete. The description is too terse to set usage context or exclusions.

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