combell_mail_zones_aliases_delete

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

Annotations already declare destructiveHint=true, but the description adds valuable side-effect context ('mail to the alias will bounce') that goes beyond the annotation. This informs the agent of the consequence, which is helpful. No contradiction; description aligns with destructive hint.

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: one sentence for the action and a clear side-effect note. It is front-loaded with the primary purpose and has zero wasted 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?

For a simple delete operation with two parameters, no output schema, and annotations covering destructive nature, the description covers the essential side effect. It does not mention prerequisites or idempotency, but these are less critical given the simplicity and annotations. The lack of domain_name documentation is a minor gap.

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 50%: email_address has a description ('The alias address to delete'), but domain_name has none. The description does not compensate for this gap, adding no meaning to either parameter. The tool name suggests domain context, but the description offers no clarification.

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 ('Delete') and resource ('an e-mail alias'), clearly distinguishing it from sibling tools like combell_mail_zones_aliases_create and combell_mail_zones_aliases_update. The action is unambiguous.

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 does not explicitly state when to use this tool versus alternatives, but the side-effect warning ('mail to the alias will bounce') implies caution and suggests it is for removing an alias. It lacks explicit when/when-not guidance or mention of sibling delete tools like combell_mailboxes_delete or combell_mail_zones_catch_all_delete.

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