Remove KeenDNS mapping

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds two genuinely new facts: protected names are refused, and dry_run defaults to true, which materially changes how an agent should invoke the tool. It stops short of 5 because it never explains what dry_run=false actually does or whether deletion is recoverable.

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, zero filler, and the destructive scope plus the dry_run default are front-loaded. Every sentence carries information an agent needs before calling.

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 two-parameter destructive mutation with full annotation coverage and no output schema, the description supplies the essential constraint (protected names) and the safety default. It leaves a small gap in not clarifying the effect of flipping dry_run to false, which is the one behavior an agent must get right to complete a real deletion.

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 both parameters, establishing a baseline of 3. The description's note that dry_run defaults to TRUE largely restates the schema's 'Default true' and adds no syntax or format detail beyond it.

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 KeenDNS mapping by name'), which cleanly separates it from set_keendns_mapping and get_keendns_mappings. It does not explicitly name those siblings, so it falls short of a 5.

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 mention that 'dry_run is TRUE by default' hints at the safe-invocation workflow, and 'Protected names are refused' signals a failure condition. However, there is no explicit statement of when to use this versus set_keendns_mapping, nor any instruction on setting dry_run=false to actually commit the deletion.

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