delete_dns_record

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

Annotations already indicate destructiveHint=true and idempotentHint=false, but the description adds valuable context beyond them: the operation is permanent, verification is advised, and certain managed record types cannot be deleted. There is no contradiction with the annotations.

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 sentences with no filler. The core purpose is front-loaded, followed by the irreversible warning and the managed-record exception. Every sentence contributes useful information.

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-param destructive tool, the description is complete: it states what is deleted, where the identifier comes from, why caution is needed, and what cannot be deleted. The annotations cover safety semantics, and no output schema is expected, so the absence of return-value detail is not a meaningful gap.

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?

The input schema fully documents both parameters with descriptions, including that recordId comes from list_dns_records and that deletion is irreversible. The tool description largely repeats that schema information rather than adding new parameter-level meaning, so the baseline 3 applies.

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 delete one DNS record'. It also identifies the source of the recordId via list_dns_records, which distinguishes this tool from add_dns_record, update_dns_record, and list_dns_records.

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 gives clear usage guidance: verify the record first and understand that deletion is irreversible. It also excludes GoDaddy-managed SOA and apex NS records. However, it does not explicitly name update_dns_record as the alternative when the intent is to modify rather than delete, so it falls just short of a 5.

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