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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds the concrete blast radius (received mail, sent copies, attachments), the irreversibility ('no undo'), and a required human-confirmation step. That is substantive behavioral context beyond the structured hints.

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 tightly packed sentences, zero filler. The destructive scope is front-loaded and the safety caution follows immediately, so an agent can act on the first clause alone.

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?

Output schema exists, so return values need no explanation, and the description covers destruction scope, irreversibility and the confirmation requirement. The only gap is that it does not contrast with the single-message delete siblings, which a caller selecting among 38 tools might want.

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?

Only one parameter (thread_id), whose uuid format and pattern are fully captured in the schema, and the description's term 'conversation' maps unambiguously onto it. With a single self-evident identifier there is little additional semantic detail the description could add, so this is near the 0-param baseline.

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?

States a specific verb ('Permanently delete') and a precisely scoped resource ('all messages currently in a conversation, including received mail, sent copies and their attachments'). The conversation-level scope distinguishes it from siblings like delete_message, delete_sent_message and delete_draft without needing to name 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?

Gives a clear operating instruction ('Confirm the exact conversation and full scope with the human') but never states when to prefer this over delete_message or delete_sent_message, nor any exclusions. Usage context is implied by the destructive scope rather than explicitly routed.

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