dns_delete_record

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

With no annotations, the description carries the burden of disclosing behavior. It does state the destructive action ('Delete') and the return type ('Status message confirming deletion'), and mentions ctx for resource change notifications. However, it does not disclose permanence, idempotency, permission requirements, or failure behavior.

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 compact and front-loaded with the main action, followed by Args and Returns sections. However, it includes a 'ctx' argument that is not present in the input schema, which could confuse an agent attempting to pass it explicitly. This reduces structural clarity.

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 delete operation, the description covers the inputs and return status, but omits useful context such as error cases, whether deletion is permanent, or how to find the record_id. Given the absence of annotations, this leaves gaps in operational guidance.

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%, so the description is the only source of parameter meaning. It defines domain as 'The domain name' and record_id as 'The record ID to delete,' which is minimal but sufficient for basic invocation. It does not explain how to obtain record_id or specify formats like FQDN or ID type.

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 action and resource: 'Delete a DNS record.' It clearly distinguishes this from sibling tools like dns_delete_domain, dns_update_record, and dns_create_record by focusing on deleting a single record via its record_id.

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 usage for deleting a DNS record but provides no explicit guidance on when to use it versus alternatives, such as dns_delete_domain or dns_update_record. It also does not mention prerequisites like looking up the record_id first via dns_list_records.

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