Delete mail account

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

With no annotations provided, the description carries the full burden. It discloses that deletion requires confirmation (confirm:true), which is a behavioral safeguard. However, it does not detail side effects (e.g., irreversibility, impact on related resources) or potential errors, leaving some opacity.

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 extremely concise—two short sentences. It front-loads the action and essential condition, with no extraneous information. Every sentence earns its place.

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 straightforward delete tool with a simple schema, the description covers the key purpose and a critical condition. The lack of an output schema means return values aren't expected, but the description could briefly mention expected outcomes (e.g., success indication). Still, it's largely complete for its simplicity.

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 both parameters already have clear descriptions. The tool description repeats the confirm requirement (already in schema), adding no new meaning. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Delete' and the resource 'mailbox' (or 'mail account'), and includes the internal name 'delete_mailaccount'. This is a specific verb+resource that distinguishes it from sibling tools like mail_add or mail_list.

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 notes the prerequisite 'Requires confirm:true', which is a key condition for usage. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., when not to use it, or scenarios where other tools might be preferred). The condition is useful but limited.

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