DNS_deleteDNSRecordsV1

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

The description indicates a mutation operation ('Delete') and states it removes specific DNS records. No annotations are provided, so description must carry the burden. It lacks details on reversibility, authentication requirements, or error handling, which are not covered.

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 reasonably concise with three sentences. It front-loads the purpose, then explains filtering and alternatives. However, the filter details could be integrated more succinctly.

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 description omits crucial information about the filter parameters that are mentioned but not present in the schema. For a deletion tool, knowing exactly which records will be deleted is essential. The absence of these parameters in the schema makes the description incomplete.

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 input schema only has 'domain' with full coverage, but the description introduces filter parameters ('name', 'type') that are not in the schema. This mismatch adds confusion rather than clarity. The description does not elucidate the existing parameter beyond its name.

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 tool deletes DNS records for a domain and distinguishes from sibling tools like DNS_resetDNSRecordsV1 and DNS_updateDNSRecordsV1 by mentioning alternative filtering. However, the mention of filters with 'name' and 'type' does not match the input schema, which only has 'domain', causing slight confusion.

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?

Explicit guidance is given: use for deleting specific records, and if multiple records with same name/type exist and partial deletion is needed, use 'Update zone records' endpoint. This provides clear context on when and when not to use. The filter instructions are useful but not fully aligned with schema.

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