web_domain_delete

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the destructive action without explaining possible cascading effects, irreversibility, required permissions, or whether related subdomains, DNS records, or aliases are affected. For a delete operation this is a meaningful gap.

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 words, front-loaded with the action, and contains no filler. Every word earns its place and there is no redundant repetition of the schema or tool name.

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 single-parameter deletion tool, the description is minimally adequate: an agent can infer it should call this with a web domain ID. However, the complete absence of behavioral context around a destructive operation leaves some ambiguity about side effects, making it less than fully complete.

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 provides 100% coverage for the single required parameter 'domain_id' with the description 'Web domain ID'. The tool description adds no parameter-level meaning beyond what the schema supplies, so the baseline of 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?

Description states a specific verb and resource: 'Delete a web domain'. This clearly differentiates from sibling tools like web_subdomain_delete, dns_zone_delete, and mail_domain_delete by naming the exact resource type being removed.

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 provides no guidance on when to use this tool versus alternative deletion tools, and no prerequisites, exclusions, or contextual conditions are given. The only implied usage is that this is the tool for deleting a web domain, but nothing explicitly addresses selection criteria.

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