delete dns record

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

Annotations already convey destructiveHint=true and readOnly=false, so the destructive nature is known. The description adds only the implementation detail that it executes 'verified command v-delete-dns-record,' without explaining side effects, irreversibility, or any confirmation requirements beyond the schema.

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 short and front-loaded with the core purpose. The second sentence adds a minor implementation detail but does not bloat the description. It is appropriately concise, though the second sentence contributes little selection value.

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 operation, the description combined with annotations and schema is minimally adequate. However, it lacks explicit guidance about the meaning of 'id' and the 'restart' parameter, and it does not warn about the destructive consequence beyond the annotation and confirm field. It is sufficient but not comprehensive.

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 20%, and the description provides no parameter guidance. The role of 'id' as the record identifier, the meaning of 'restart', and why 'confirm' must be true are not addressed in the description. Only the schema documents 'confirm,' leaving 'restart' and other parameters under-explained.

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 action and object: 'Delete a DNS record.' This distinguishes it from sibling tools like delete_dns_domain or add_dns_record. Mentioning the underlying command reinforces the specific operation without ambiguity.

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 implies this tool is for deleting an individual DNS record, but it does not explicitly state when to use it versus alternatives such as delete_dns_domain for deleting a whole domain. No exclusions or alternative tool routing are provided.

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