delete_dns_record

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

Annotations declare readOnlyHint=true and destructiveHint=false, which a bare 'delete' name would seem to contradict; the description resolves that by explaining this is a preview that shows current contents. It adds the reason behind the safety hints, though it omits whether the preview expires, what the output contains, or how the real deletion is triggered.

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?

A single front-loaded sentence with no filler; the critical 'Preview' qualifier comes first. Brevity here shades into under-specification rather than being genuinely efficient.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. However, with 0% parameter coverage and no pointer to how the deletion is actually applied, an agent lacks enough to use this confidently in a workflow.

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 0% for both parameters, so the description carries the burden. 'Exact DNS record' hints that record_id selects a single record, but it never explains whether 'domain' is a name or an ID, nor the accepted string/integer duality.

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+resource: previewing deletion of a DNS record, with the qualifier 'exact' implying record_id-level targeting. It is distinguishable from list_dns_records/get_dns_record/update_dns_record, though it never names which sibling performs the actual deletion.

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?

No when-to-use or when-not-to-use guidance, and no indication of what to do after previewing (e.g., apply_plan or a confirm step). The word 'Preview' implies a read-only inspection step but the workflow is left to inference.

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