delete_dns_forwarder_host_override

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

Annotations already declare destructiveHint=true, and the description adds a meaningful 'irreversible' warning, which goes beyond the annotation's generic destructiveness. It does not mention the confirm/dry_run safety gates, but those are fully described in the schema, so no contradiction exists.

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 short sentences, with the action front-loaded and the warning delivered immediately. Every word earns its place, and there is no repetitive or filler content.

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 simple delete tool, the description combined with 100% schema coverage, annotations, and an output schema is nearly complete. It adds the important irreversibility caveat, though it could mention that confirm=true is required to execute, but the schema already covers that.

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 baseline is 3. The description adds no parameter-specific detail beyond saying 'by ID', while the schema already explains override_id source and safety flags. The description provides no extra semantic value over the schema.

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 clearly states the tool deletes a DNS Forwarder host override by ID, using a specific verb and resource. It distinguishes from nearby sibling tools like delete_dns_host_override and delete_dns_domain_override by naming 'DNS Forwarder' 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?

The description provides no guidance on when to use this tool versus alternatives, such as delete_dns_host_override or delete_dns_domain_override. It does not mention prerequisites like searching for the ID first or that confirm must be true to execute, leaving usage entirely implied.

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