Delete domain

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

With no annotations provided, the description carries full responsibility. It explicitly discloses permanence ('PERMANENTLY', 'cannot be undone'), cascading deletion of mailboxes and stored emails, and the need for confirmation. This is fully transparent for a destructive operation.

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, front-loaded with the critical warning ('PERMANENTLY delete'), and every phrase contributes meaning. There is no redundant or filler content, making it highly concise and well-structured.

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?

Despite lacking an output schema and annotations, the description thoroughly covers all critical aspects for a destructive tool: exactly what gets deleted, irreversibility, and the confirmation requirement. For a two-parameter tool, this is comprehensive and sufficient.

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?

The input schema already has 100% description coverage for both parameters ('name' and 'confirm'), including a clear explanation of the confirm constraint. The description reinforces 'Requires confirm=true' but does not add additional meaning beyond what the schema already provides, so the baseline 3 is appropriate.

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 uses a specific verb ('delete'), resource ('domain'), and scope ('ALL of its mailboxes, including every stored email'), clearly distinguishing it from sibling tools like delete_mailbox or delete_alias. It leaves no ambiguity about what the tool does.

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?

The description clearly indicates the use case: permanently removing an entire domain and all associated mailboxes/emails. It also states the confirm=true requirement. However, it does not explicitly name alternatives or when not to use it (e.g., 'use delete_mailbox for single mailbox deletion'), so it falls short of a 5.

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