delete_dns_records

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

No annotations are provided, so the description must carry safety/behavioral disclosure. It states deletion and requires exact record data, but doesn't disclose irreversibility, failure semantics, or effect on existing records. This is a notable gap for a destructive tool.

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?

Two sentences, front-loaded with the primary action. The prerequisite sentence is essential and not redundant. No filler.

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 structurally simple with two parameters fully documented, but no output schema or annotations. The description covers purpose and a key prerequisite, yet omits operational context like irreversibility or how to obtain exact record data (e.g., via list_dns_records). Overall adequate but with room for more 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?

The schema documents all parameters with 100% coverage, so baseline is 3. The description adds 'matching the existing record,' reinforcing the exact-match requirement already noted in the records schema description, but provides little additional syntax or format guidance.

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 opens with 'Delete DNS records for a domain,' a specific verb+resource statement. It clearly distinguishes this tool from list/create/update siblings since it is the only deletion tool. The addition about full record data further clarifies the operation.

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 when to use: to remove DNS records for a domain. It gives a prerequisite ('Requires full record data matching the existing record') but doesn't explicitly reference sibling list_dns_records or state when not to use. Because it is the sole delete tool, the intended use is reasonably clear.

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