ecp_domains_delete

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

With no annotations, the description carries the behavioral burden and explicitly states 'Irreversible,' which is critical for a destructive tool. It also discloses the primary-domain restriction. It does not describe downstream effects on subdomains or DNS records, but the core safety-relevant behaviors are covered.

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?

Three short sentences convey the action, a key restriction, and irreversibility with no wasted words. The most important operational facts are front-loaded.

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 tool is simple, and the description covers the action, a major constraint, and durability of the operation. However, it lacks guidance on what happens if the primary domain is attempted, what confirm must be set to, and whether related DNS or subdomain records are affected, leaving some context gaps given no annotations or output schema.

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 0%, so the description must compensate for parameter meaning, but it only implicitly references 'domain' and says nothing about the required 'confirm' parameter or the domain format. The 'confirm: true' constraint is left entirely to the schema.

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 and resource: 'Delete a domain from this account.' It also adds a key differentiating constraint, 'Cannot delete the primary domain,' and the verb 'delete' clearly separates it from sibling tools like ecp_domains_add_domain and ecp_domains_set_redirect.

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 usage context is implied by the verb and resource—use this when you need to remove a domain. It provides one when-not condition ('Cannot delete the primary domain') but does not mention alternatives or any prerequisite step such as listing domains first.

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