adm_dns_delete

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

With no annotations provided, the description carries the full burden of disclosing behavior. 'Delete' already signals destructiveness, and '(careful!)' adds a cautionary tone. However, it does not explicitly state that deletion is irreversible or describe any side effects, so depth is limited.

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 sentence with no filler. 'Delete a DNS record' is immediately actionable, and '(careful!)' is a compact, useful warning that earns its place.

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?

This is a simple one-parameter delete tool with no output schema, and the schema fully documents the only parameter including its source. The description plus schema is sufficient for an agent to invoke the tool correctly, though it could have explicitly mentioned irreversibility.

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 description coverage is 100%, and the schema already explains that subdomain_id is the DNS record ID from adm_dns_records. The tool description itself adds no parameter-level detail beyond the domain context, so it meets the baseline but does not exceed it.

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 specific action ('Delete') and a clear resource ('DNS record'), so an agent immediately knows what the tool does. It is also easily distinguished from sibling tools such as adm_dns_add and adm_dns_records, which handle creation and listing rather than deletion.

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 gives no explicit guidance on when to use this tool versus alternatives, and it does not mention any prerequisites or exclusions. The 'careful!' warning implies cautious use, but there is no clear routing to or away from sibling tools.

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