Delete a chat message

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

Annotations already indicate destructiveHint=true, and the description confirms deletion. However, no additional context is given about irreversibility, confirmation, or side effects (e.g., whether the delete propagates to all users, or if it requires specific moderation privileges). The description adds no behavioral details beyond what annotations and schema imply.

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 a single sentence of 9 words, which is concise and focused. It front-loads the action and resource, making it easy to parse. No unnecessary information is included.

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 the tool's simplicity (2 params, no output schema), the description is adequate but lacks context about the result (e.g., success confirmation, error cases, or implications of the destructive action). The absence of return value documentation is acceptable since no output schema exists, but the description could mention that the action is irreversible.

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%, with each parameter having a brief description. The tool description does not add any semantic value beyond what is already in the schema (e.g., no explanation of how platform affects deletion or what values message_id can take). Baseline score of 3 applies since schema does the heavy lifting.

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 clearly states the action (delete) and the resource (chat message) with a specific identifier (message id). It distinguishes delete_message from siblings like clear_chat (which clears all messages) but does not explicitly differentiate from moderate_user which may also delete 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?

No guidance is provided on when to use this tool versus alternatives (e.g., clear_chat, moderate_user). There is no mention of prerequisites, permissions, or conditions under which deletion should be used, leaving the agent to infer based on tool name alone.

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