delete_message

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

Without annotations, the description partially fills the gap by disclosing the self-delete restriction. However, it does not mention permanence, return value, or error cases, leaving some behavioral ambiguity.

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?

Single sentence is concise, front-loaded with the official API tag, and efficiently conveys the core action and constraint without redundancy.

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 tool with one parameter and no annotations, the description adequately explains the key limitation. Minor gaps remain (e.g., no output schema or error handling), but overall it is complete enough for its 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 a clear parameter description. The tool description adds no extra semantic value for the message_id parameter beyond what the input schema already provides.

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?

Clearly states verb 'delete' and resource 'message', and includes the critical constraint that a bot can only delete its own messages, differentiating from sibling tools like update_message or delete_reaction.

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?

Implicitly provides usage context by stating the self-only limitation, helping an agent decide when to use (own messages) and when not to (other users' messages). However, it lacks explicit direction on alternatives.

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