Delete DNS record

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

Annotations already mark the tool as destructive and non-read-only. The description adds meaningful behavioral context by disclosing mandatory optimistic-concurrency guards and the read-before-delete workflow, which helps the agent avoid failed or stale deletions.

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?

Two tightly packed sentences: the first names the operation and its defining guard requirement, the second gives the necessary precondition. No filler or redundant restatement.

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 covers the essential precondition and the meaning of the required parameters for a destructive 4-parameter operation, while the output schema handles return-value expectations. It could be slightly stronger by naming get_dns_record as the read step, but it is still complete enough for correct use.

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?

With 0% schema description coverage, the description compensates by explaining that expected_value and expected_priority are observed-state guards rather than arbitrary values. Domain and record_id remain self-explanatory from their names, but are not explicitly described; the critical guard semantics are well covered.

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 and resource: 'Delete a DNS record'. This directly distinguishes it from the sibling list/get/create/update operations, and the additional guard details clarify what form of delete this tool performs.

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?

It gives clear operational context: callers must read the record first and supply the observed state as expected_value and expected_priority. It does not explicitly name alternative tools or exclusions, but the precondition and invocation guidance are unambiguous.

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