Remove static DNS record

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

Goes well beyond the annotations by disclosing that dry_run defaults to TRUE — critical for a destructive tool — and that the address is resolved from the config tree because the router's removal form needs both fields. Annotations already flag destructive/idempotent, and the description adds the operational nuance that would otherwise cause a surprise deletion.

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?

Four short sentences, front-loaded with the action and the wire-level command, then the non-obvious caveats. No filler.

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 destructive, no-output-schema tool, everything needed is present: safety default (dry_run), parameter resolution rules, and the recovery path via set_dns_host. Nothing material is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: the address parameter's resolution-from-config behavior and the consequence of omitting it are explained rather than just 'Address, only needed if the name has several'.

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 ('Delete a static DNS record'), quotes the underlying CLI form, and distinguishes itself from the sibling set_dns_host by naming the inverse operation. An agent can tell exactly what this 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?

Explains the key conditional: address is normally looked up automatically and should be passed only to disambiguate a duplicated name. It also names set_dns_host as the re-create path, though it never mentions read-side siblings (e.g. get_dns_proxy/keendns mapping listing) for verification.

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