delete_dns_host_override

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

The description adds a clear 'WARNING: This is irreversible' which goes beyond the destructiveHint annotation by emphasizing permanence. It does not mention safety gates like confirm or dry_run, but the annotations already signal the destructive nature, and the warning provides useful extra context.

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: the first states the action and target, the second gives a critical warning. No filler or redundant phrasing; the structure is front-loaded and effective.

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?

The tool has an output schema, annotations, and a schema covering all parameters, so the description does not need to explain return values or parameter formats. The only minor omission is the workflow for applying changes (e.g., apply_immediately), but the schema covers that. Overall the total definition is sufficient for understanding the tool.

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 schema already documents all four parameters. The description adds no additional parameter semantics beyond confirming the 'by ID' lookup, which is already in the override_id parameter description. It neither helps nor hinders beyond the baseline.

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 starts with a specific verb ('Delete') and resource ('DNS host override by ID'), clearly distinguishing it from related tools like delete_dns_domain_override or delete_dns_forwarder_host_override. The action and scope are unambiguous.

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 'by ID' phrasing implies the need to first search for the override identifier, but the description does not explicitly mention search_dns_host_overrides as a prerequisite or provide guidance on when to use this tool versus alternatives. No exclusions or workflow steps are given, making this minimal but not misleading.

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