dns_delete_record

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

With no annotations, the description carries the burden of disclosing behavioral traits. It notes the confirm=true gate, which implies a safety mechanism and that deletion will not occur without it. However, it does not explicitly mention irreversibility or potential impacts of deleting the record, leaving room for more transparency.

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 one concise, front-loaded sentence covering the essential action and key requirement. No wasted words.

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 is minimal but sufficient for a delete operation: it states the action and the critical confirm parameter. However, with no annotations and no output schema, it does not elaborate on preconditions or consequences of deletion, making it only minimally 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 schema covers 100% of parameter descriptions, including the confirm parameter's behavior. The description adds emphasis on confirm=true but does not provide additional meaning beyond the schema. Baseline 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 clearly states 'Delete a specific DNS record from a zone' with a specific verb and resource. It distinguishes itself from sibling tools like dns_delete_zone or dns_update_record by specifying a single record deletion. The addition of the confirm requirement 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 mentions the confirm=true requirement but does not explicitly explain when to use this tool versus alternatives like dns_update_record or dns_add_record. The intended use is implied by the name and description but lacks explicit 'when not to use' guidance.

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