Delete Dns Record

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

No annotations are provided, so the description carries the full burden. It discloses a precondition (SUBREG_READONLY must be false) which implies the tool is a write/delete operation, but it does not elaborate on side effects, permanence, or error behavior. The requirement adds value but lacks depth.

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 a single, front-loaded sentence with no filler. Every word contributes to understanding the tool's purpose and a key requirement.

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?

The tool is simple with only two parameters, but without an output schema or annotations, the description omits expected return values and failure modes. The precondition is helpful, but overall completeness is adequate but not thorough for an unannotated delete operation.

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 must compensate. It mentions 'record id' and 'zone' which hint at the parameters record_id and domain, but does not explain what 'domain' represents or how to obtain the record_id. This is minimal value, insufficient for no schema coverage.

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 function: 'Delete a DNS record from a zone by its record id.' It uses a specific verb and resource (delete DNS record) and distinguishes it from sibling tools like add_dns_record and delete_domain.

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 provides a condition: 'Requires SUBREG_READONLY=false,' which is a useful context for when the tool can be used. However, it does not explicitly mention when to use this tool versus alternatives, nor does it state exclusions.

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