Delete messages

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

Discloses the irreversible nature of permanent deletion and the recoverability of default deletion. Annotations already mark destructive and idempotent, but the description adds concrete details about the default behavior and recovery path.

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?

Two concise sentences, each packed with essential information. No redundant words or unnecessary details.

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 complexity, it covers all key aspects: action, limits, default vs permanent behavior, recovery, and idempotency. The output schema exists but is not needed for the description to be complete.

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 descriptions cover both ids and permanent with constraints. The description reinforces these by explaining the effect of permanent and the recovery mechanism, adding value beyond the schema.

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 action (delete) and the resource (messages), with a specific limit of up to 500 ids. It implicitly distinguishes from sibling tools like mail_move and mail_search.

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 explains the default behavior (move to Deleted Items) versus permanent deletion, and notes recovery via mail_search and mail_move. It also instructs to use permanent only when explicitly requested, providing clear usage guidance.

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