domains_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 confirms the operation is a deletion and mentions that confirm is required, but it does not state whether the deletion is irreversible, cascades to associated DNS/email/subdomains, or requires specific permissions. An agent cannot predict the destructive scope beyond what the tool name already implies.

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 short, front-loaded, and contains no filler. The single-sentence purpose followed by a compact Args block is easy to scan. However, the terseness omits important behavioral and semantic details, so the structure is good but not excellent.

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?

This is a destructive mutation tool with no annotations and minimal schema descriptions, so the description must cover consequences and prerequisites. It mentions impersonation and confirmation, but it does not explain what happens to the domain or associated resources, nor does it clarify the required confirm value. The existence of an output schema does not compensate for missing behavioral context.

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 schema has 0% description coverage, so the description must compensate. It adds one useful piece of meaning ('impersonate: Owning user'), but 'domain' and 'confirm' mostly restate their titles. More seriously, 'confirm: Required' conflicts with the schema, which lists only domain as required and gives confirm a default of false; this makes it unclear whether a truthy confirm value must be sent.

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 an account.' This is clear and distinguishes the tool at the domain level from subdomain or domain-pointer deletion tools. It does not explicitly differentiate itself from siblings, so it is clear but not fully differentiated.

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?

There is no guidance on when to use this tool versus alternatives like domains_create, subdomains_delete, or domain_pointers_delete. The description only restates the action and lists arguments; it gives no 'when to use' or 'when not to use' context. The mention of confirm and impersonate is operational, not usage-selection guidance.

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