Delete DNS Record

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds valuable operational context beyond annotations: deletion is permanent, explicit confirmation is required, and unknown outcomes should not be retried automatically.

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 sentences, front-loaded with the core action and followed by the key operational constraint. Every sentence earns its place with no redundancy.

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?

Annotations carry the safety profile and the schema marks dns_record_id as required, but the description omits which parameters are required and does not clarify zone/account scoping. For a destructive tool with no output schema and 50% parameter coverage, this is adequate but leaves notable gaps.

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 only 50%, and the description does not explain any parameters. It alludes to confirmation but never mentions the 'confirm' parameter, nor does it clarify 'dns_record_id', 'zone_id', or 'account' beyond what the schema already provides.

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 states a specific verb and resource: 'Permanently removes a DNS record from the zone.' This clearly distinguishes it from sibling read, create, update, and overwrite tools without needing to inspect schemas.

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?

It provides an invocation guideline—'Every change requires explicit confirmation; never repeat an unknown outcome automatically'—but does not state when to use delete_dns_record rather than update_dns_record, overwrite_dns_record, or other destructive siblings. Usage context is implied but not differentiated.

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