Delete DNS record

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description reinforces it with '[DESTRUCTIVE] Permanently delete'. It adds genuinely new behavioral context by forbidding inference of record_id and forbidding multi-delete, which no annotation conveys. It does not describe failure modes or post-delete effects on CDN behavior.

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?

Three short, front-loaded fragments: destructive flag first, action second, constraint third. No filler and every clause carries operational value.

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?

For a destructive mutation with annotations and no output schema, the description covers the safety profile, the id precondition, and the endpoint. It is nearly complete; only edge behavior (irreversibility confirmation, effect on related records/domain resolution) is left implicit.

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% (record_id documented, domain only constrained by pattern), so the schema carries part of the load. The description adds meaning for record_id ('exact... never infer'), but says nothing about the domain parameter or id format beyond that. Baseline 3 fits a 2-param tool where the schema does most of the work.

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?

States a specific verb and resource (permanently delete one DNS record), flags it as destructive up front, and gives the exact API endpoint. It is trivially distinguishable from the sibling DNS tools (list/get/create/update_dns_record) without opening any schema.

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?

Provides a clear guardrail — 'Requires exact record_id — never infer or delete multiple' — plus the note that the id comes from list/get_dns_record (in the schema). It does not explicitly name a sibling tool or describe prerequisites/escalation paths, so it stops short of full when/when-not guidance.

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