Delete Domain

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

No annotations are provided, so the description must fully disclose behavioral traits. It does reveal a permission requirement (SUBREG_READONLY=false), but it omits critical side effects of a destructive operation such as irreversibility, impact on DNS records, or refund policies. This is insufficient for a delete tool.

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 a single sentence containing only essential information: the action and the prerequisite. It is concise, front-loaded, and free of unnecessary 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 destructive tool with no output schema and no annotations, the description is severely under-specified. It lacks usage context, post-deletion effects, and any mention of alternatives or error conditions, making it only marginally more helpful than the tool name itself.

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%, and the description does not elaborate on the 'domain' parameter beyond its name. It fails to specify expected format (e.g., example.com vs. punycode), whether it expects a domain ID or name, or any other constraints, forcing the agent to rely on the parameter name alone.

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 'Delete (cancel) a domain registration' with a specific verb and resource. This distinguishes it from the sibling tool 'delete_dns_record' and other domain management tools like 'register_domain' and 'renew_domain'.

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 alternatives. It only mentions a prerequisite (SUBREG_READONLY=false) but does not compare with register_domain, renew_domain, or delete_dns_record, leaving the agent without clear selection criteria.

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