delete_dns_domain_override

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

The description adds 'WARNING: This is irreversible,' going beyond the destructiveHint annotation by specifying permanence. This is useful behavioral context. However, it does not mention the confirm/dry_run safety gates, which are documented in the schema.

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 two concise sentences: the action is front-loaded, and the warning is direct. There is no redundancy or unnecessary detail, making it efficiently structured.

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?

Given that annotations cover destructiveness, the schema fully describes parameters (including the confirm gate), and an output schema exists, the description is sufficiently complete for a simple delete operation. It lacks explicit usage guidance but is otherwise adequate.

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%, so the tool description adds no parameter-level meaning. The schema already provides informative descriptions, including the override_id source from search_dns_domain_overrides, so a baseline score of 3 is appropriate.

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 uses the specific verb 'Delete' and resource 'DNS domain override', making the operation clear. However, it does not explicitly contrast with other delete tools for different override types (e.g., host overrides), so it lacks direct sibling differentiation.

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 gives no guidance on when to use this tool versus alternatives, such as when to use delete_dns_host_override or how to obtain the override ID. It only states the action without context on prerequisites or exclusions.

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