domains_deletePermanently delete a domain. You MUST confirm with the user before calling this tool, referencing the domain name.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name to delete (e.g. "www.example.com") |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already signal destructiveness and non-read-only behavior, and the description adds context by emphasizing permanence and requiring user confirmation before invocation. This goes beyond the annotation labels, though it does not describe cascading effects such as what happens to associated DNS records.
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?
Two short sentences deliver the core purpose and the single most important operational requirement. There is no filler, and the confirmation instruction is placed prominently after the action statement.
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 single-parameter destructive tool with no output schema and strong annotations, the description provides everything an agent needs to decide and safely invoke the tool: what is deleted, that deletion is permanent, and that user confirmation is mandatory.
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 covers 100% of the single parameter with a clear description, so the baseline is 3. The tool description does not add additional semantic detail about the parameter beyond the schema, aside from implying the domain name should be referenced during confirmation.
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 the specific action ('Permanently delete a domain') with a clear resource, and the destructive nature makes it easy to distinguish from siblings like domains_set, domains_get, and domains_list. It unambiguously identifies what the tool does.
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 clearly communicates the critical precondition: 'You MUST confirm with the user before calling this tool, referencing the domain name.' However, it does not explicitly contrast with alternatives, such as when to use domains_set instead of delete, so it falls just short of full guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Deployment tools and domain tools are cleanly separated by resource prefix, and each tool targets a distinct action (list/get/upload/delete/set vs validate/set/records/verify). The few related domain tools—dns, records, share, verify—have clear boundaries around provider lookup, record display, shareable links, and verification triggering.
Tool names consistently follow a resource_action pattern: deployments_* and domains_* with clear verbs. The only deviation is whoami, which is a conventional standalone name but does not follow the noun_verb structure; this is a minor exception.
Fifteen tools is at the upper end of the ideal range but every tool serves a distinct purpose within the static-hosting and custom-domain lifecycle. There is no apparent redundancy or bloat.
The deployment surface covers upload, read, list, update labels, and delete, while the domain surface covers validation, creation/update, details, listing, DNS records, verification, sharing, and deletion. The account check via whoami rounds out the lifecycle with no obvious dead ends.