Delete Inbox Message

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

Descriptors 'permanently delete' and 'already in Trash or Junk' add behavioral context beyond annotations. Annotations already mark destructiveHint=true and idempotentHint=true, and description aligns without contradiction.

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 sentences, no wasted words. The key information (what it does, prerequisite, alternative) is front-loaded and immediately actionable.

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 annotations (destructiveHint, idempotentHint) and 100% schema coverage, the description is sufficient. It could mention the optional idempotency_key, but the schema already covers it. Output schema exists, so return values are not needed.

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%, so baseline is 3. The description adds value by clarifying that the message_id parameter must refer to a message in Trash/Junk, which is not explicit in the schema properties.

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: 'Permanently delete one inbox message that is already in Trash or Junk.' It distinguishes from the sibling tool shipmail_move_inbox_message by specifying the prerequisite and alternative.

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?

Provides explicit guidance: only use when the message is already in Trash or Junk, and directs to shipmail_move_inbox_message for moving to Trash. This clearly specifies when to and when not to use the tool.

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