Delete email

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

Annotations already declare destructiveHint=true, but the description adds materially: the default is a recoverable move to Trash, permanent=true is irreversible (flagged with a warning glyph), and the target mailbox must be a real folder. It does not cover auth/permission needs or success return, keeping it below a 5.

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?

Three short sentences, zero filler, with the default behavior stated first and the destructive escalation second. Every sentence carries information an agent needs to call the tool safely.

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 4-parameter mutation with annotations and no output schema, the description covers reversibility, the destructive option, and the folder prerequisite. It is slightly thin on what a successful deletion returns and on account/emailId sourcing, but nothing critical to correct invocation is missing.

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 3 is the baseline, but the description adds semantics not in the schema: the mailbox must be a real (non-virtual) folder, which explains why find_email_folder may be needed. It also reinforces the irreversible nature of the permanent flag beyond the schema's brief note.

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 and resource ("Delete an email") and immediately qualifies the operation's scope: default soft-delete to Trash versus permanent removal. This distinguishes it from siblings like delete_label, delete_mailbox, and bulk_action, which operate on different resources.

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 concrete prerequisite and routes the agent to a sibling tool ("Use find_email_folder first if the email was found in a virtual folder") and explains the condition that selects the permanent path. It does not mention when to prefer bulk_action for multiple messages, so it stops short of full alternative coverage.

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