delete_message

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

The description only states the action 'Delete' without disclosing behavioral traits such as irreversibility, permission requirements, side effects, or cascading deletions. Since no annotations are provided, the description carries full responsibility for behavioral disclosure and fails to do so.

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, clear sentence with no redundancies. Every word serves a purpose (verb, resource, method). It is appropriately concise for a simple delete operation.

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 straightforward delete operation with one parameter and no output schema, the description is minimally adequate. However, it lacks context about the effect (e.g., permanent deletion, impact on related data) which would be valuable given sibling tools like update_message_status imply a status lifecycle.

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 has 100% description coverage, adequately defining 'messageId' as 'Message ID to delete'. The description adds no additional semantic value, merely restating the schema's information. Baseline score of 3 applies due to high schema coverage.

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 (contact message), and specifies the identifier (by its ID). It implicitly differentiates from sibling delete tools (e.g., delete_post, delete_comment) by indicating the resource type is 'contact message', though it does not explicitly contrast them.

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., update_message_status for soft operations). There are no exclusions or prerequisites mentioned, leaving the agent to infer usage purely from the action verb.

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