Delete Dns Record

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

There are no annotations, so the description carries the behavioral disclosure burden. It explicitly reveals that the operation is gated behind CF_ALLOW_DESTRUCTIVE=true, signaling both the destructive nature and the likely failure mode if the flag is unset. It does not detail irreversibility effects, but the tool is a straightforward delete.

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 only two sentences, with the action stated first and the critical safety prerequisite stated immediately after. There is no filler or redundancy.

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 two-parameter deletion tool with an output schema present, the description covers the essential action and the important guardrail flag. It could mention recovery or side effects, but the flag plus clear verb makes it sufficiently complete for an agent to call it correctly.

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 coverage for parameters is 100%, and the schema already provides clear descriptions for zone_id and record_id. The description adds no additional parameter-specific semantics, so the baseline score of 3 is appropriate.

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 clear verb and resource: 'Delete a DNS record.' This directly distinguishes it from sibling tools like create_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 provides a clear prerequisite: 'Requires CF_ALLOW_DESTRUCTIVE=true,' which is useful operational guidance. However, it does not explicitly explain when to choose this over alternatives or mention any exclusion conditions beyond the environment flag.

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