delete-me-dns-record

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

The description states 'Permanently delete a DNS record' and 'Destructive and NOT reversible', which aligns with and adds context beyond annotations (destructiveHint=true). The annotation idempotentHint=true might appear contradictory, but the description's emphasis on irreversibility clarifies that the operation, while idempotent in HTTP sense, has permanent effects. No contradiction.

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 followed by a crucial warning. Both are essential and concise; 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 sufficient for a tool with only two well-described parameters and no output schema (common for delete operations). Combined with annotations, it provides complete contextual information for safe usage.

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%, so the baseline is 3. The description does not add any extra information about the parameters beyond what the schema provides, but that's acceptable since the schema is thorough with descriptions and pattern constraints.

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 'Permanently delete a DNS record from an owned domain', which uses a specific verb (delete) and resource (DNS record). It distinguishes itself from siblings like 'create-me-dns-record' and 'update-me-dns-record'.

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 explicitly warns 'Destructive and NOT reversible — confirm with the user before calling', providing clear guidance on when to use (with user confirmation) and why caution is needed. This differentiates it from read-only tools.

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