dnsDeleteRecord

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It states that a record is deleted, which implies destructiveness, but it does not mention irreversibility, propagation effects, authorization requirements, or any side effects. The API reference link may help, but it does not provide inline behavioral context.

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 concise sentence that states the core purpose and includes a reference link. There is no wasted wording, and the essential action is front-loaded.

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 two well-documented parameters, so the schema covers the invocation details. However, with no annotations and no output schema, the description is quite minimal and does not explain destructive behavior or expected return format. The external API reference partially compensates, making this minimally adequate but not complete.

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 has 100% coverage, documenting both 'domain' and 'rrid' with descriptions. The tool description adds no additional parameter meaning, but the schema already explains that rrid is the 'Record ID from dnsListRecords', which is sufficient context for correct invocation.

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 action ('Delete') and the resource ('a DNS resource record'), which distinguishes it from sibling tools like dnsListRecords, dnsAddRecord, dnsUpdateRecord, and dnsSecDeleteRecord. The verb is specific and the resource is unambiguous.

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 the tool (when a DNS resource record must be deleted) but provides no explicit guidance about prerequisites, alternatives, or exclusions. The schema's note that rrid comes from dnsListRecords gives some context, but the description itself offers no usage direction.

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