delete-message

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

Discloses destructive nature, need for user confirmation, and prior id verification via search/list. Lacks details on id format or error handling but given no annotations, this is sufficient.

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?

Four concise sentences with clear structure: use cases, return value, exclusions, safety. No 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?

Covers purpose, usage, safety, and return. Lacks details on id format or error scenarios, but for a single-parameter delete tool, it is mostly complete. Output schema exists but not needed for completeness.

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 0%, and description only mentions 'by id' without explaining format or constraints. The schema pattern provides the format, but description adds no extra meaning.

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 the tool deletes a single message by id and moves it to Trash. Differentiates from batch-delete-messages and move-message in the description.

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?

Explicitly includes 'Use when,' 'Do not use when,' and references alternatives (batch-delete-messages, move-message), providing clear context.

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