Delete DNS record

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is destructive ('Delete') and that a confirmation parameter must be set to true. This is transparent about the core behavior, though it does not cover edge cases or error responses.

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 extremely concise: one sentence with a parenthetical. It is front-loaded with the verb 'Delete'. Every part serves a purpose with 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?

Given no output schema and no annotations, the description is minimal. It covers the basic action and a key requirement, but does not explain success behavior, error handling, or record_id format. For a simple deletion tool it may suffice, but more detail would improve completeness.

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 coverage is 50%; only 'confirm' has a description. The description adds 'Requires confirm:true' which clarifies the boolean must be true to actually delete. It does not explain 'record_id' format or meaning beyond being an identifier. The description partially compensates for the low schema coverage.

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 is to delete a DNS record by ID. The parenthetical 'delete_dns_settings' may be extraneous but does not detract. The tool name and title reinforce the purpose, and it is distinct from sibling tools like dns_add, dns_list, dns_update.

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 'Requires confirm:true' as a usage condition, but does not explicitly state when to use this tool versus alternatives. There is no mention of prerequisites, typical scenarios, or exclusions. The guideline is present but minimal.

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