Delete Domain

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the concrete blast radius beyond that flag: mailboxes and forwarders under the domain stop working and inbound mail is no longer handled. It does not say whether deletion is immediate or reversible (e.g. a grace period), which is the remaining behavioral gap for a destructive operation.

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 with zero waste: action first, consequences second, safer alternative last. Every sentence earns its place and the destructive warning is 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?

With one required parameter, full schema coverage, an output schema, and annotations carrying the safety profile, the description covers what an agent needs to call it and what will break. Minor gap: it does not state whether the removal is permanent or whether prerequisites (e.g. no active pointers) apply.

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 100% and the single 'domain' parameter already documents format and an example, so the baseline of 3 applies. The description adds no additional meaning about the parameter, such as whether the domain must be verified or owned by the account first.

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?

States a specific verb and resource ('Removes the domain from the account'), scoped to this account. It is clearly distinguishable from the sibling delete_domain_pointer (which deletes a pointer, not the domain) and from set_domain_mail_hosting by naming that alternative explicitly.

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?

Gives an explicit alternative and the condition that selects it: use set_domain_mail_hosting to pause mail service without deleting the domain. The agent can decide between destructive deletion and temporary suspension without inference.

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