delete_dns_record

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

No annotations provided. Description states the action is deletion but does not disclose irreversibility, permissions needed, or other behavioral traits. Adequate for a simple operation but could add warnings.

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 sentences, no fluff. Efficiently conveys the action and identification methods.

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?

Fairly complete for a simple delete tool with 3 params, 1 required, no output schema. Covers main action and identification. Could mention deletion is immediate/irreversible for 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?

100% schema coverage, but description adds value by clarifying that record_id comes from list_subdomains and record_type is used when record_id omitted. Adds context beyond schema descriptions.

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 'Delete a single DNS record from a subdomain' with a specific verb and resource, and distinguishes from sibling tools which are mostly list/check/register operations.

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 clear guidance on how to identify the record (by record_id or record_type when subdomain has exactly one of that type), and references list_subdomains as source for record_id. Could explicitly mention when to not use it, but context makes it clear.

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