Delete Email Inbox

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

Beyond the destructiveHint annotation, the description explains that deletion revokes mailbox access, does not read messages or extract codes, incurs no additional charge, and should be preceded by reading needed messages. These are concrete behavioral consequences that help an agent act safely.

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?

The description is four compact sentences and front-loads the action and scope. Each sentence adds a distinct operational detail, including the deletion warning and parameter source.

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?

The definition is complete for a destructive deletion tool: annotations declare destructiveness, the schema fully covers parameters, an output schema exists, and the description adds timing, source, and safety guidance. Nothing essential is missing for correct invocation.

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 description coverage is 100%, so the schema already documents the three parameters. The description adds useful provenance by saying inbox_id, capability, and access_token should come from create_email_inbox, though it does not clarify that access_token is optional in some existing-connection cases.

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 states a specific verb and resource: delete an existing inbox and revoke access to its mailbox content. It also distinguishes the operation from reading messages or extracting codes, so an agent can tell it apart from list_email_messages and get_email_code.

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?

It gives a clear usage condition: use after testing is complete, and read needed messages before deleting. It also says the operation does not read messages or extract codes, which implicitly points to the read/extract siblings, but it does not explicitly name them as alternatives.

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