delete_email_account

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

No annotations are provided, so the description carries full burden. It discloses that the action is irreversible ('Esta acción no se puede deshacer'), requires confirmation, and tags it as [mutation]. This gives sufficient behavioral context for safe usage.

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 very concise: two sentences plus a tag and a note. It front-loads the key purpose and safely, with no extraneous words.

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 description covers the effect (deletes account and emails), safety (irreversible, requires confirmation), and the confirm parameter. No output schema exists, but given the tool's finality, the description is adequate for an agent to decide and invoke correctly. Minor gap: does not specify if any error or success response is returned.

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?

Input schema covers both parameters with descriptions (id and confirm). The description adds value by reinforcing the confirmation requirement and the irreversible nature, though schema coverage is 100%. A slight bump from baseline 3 due to added context.

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?

Description explicitly states 'Eliminar cuenta de email — Elimina una cuenta de correo y todos sus emails asociados.' It clearly identifies the action (delete), resource (email account), and scope (including all associated emails). This distinguishes it from other delete tools among siblings.

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 that confirmation is required (confirm=true) and the action is irreversible, implying it should be used with care. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., deactivating or archive options) nor when not to use it, leaving some ambiguity.

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