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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds material context those hints cannot convey: the record lives in the customer's own Cloudflare account, Ankra cannot restore it, and deletion takes the hostname down immediately for live traffic. This is exactly the added value expected of a destructive tool with annotations present.

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?

Front-loaded with the action, then escalating risk (irreversible, live traffic), then the required procedure, then the edge case. Four sentences, none of them filler, ordered by importance to the caller.

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?

Covers everything an agent needs for a 3-parameter destructive call with no output schema: irreversible consequences, user-confirmation workflow, id discovery, credential resolution, and the external-record caveat.

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 domain_id, record_id and credential_name are already documented in the schema, including where to discover the ids. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 ('Delete a DNS record') and scopes it to the organisation's Cloudflare domains, which separates it cleanly from create_cloudflare_dns_record and update_cloudflare_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?

Gives an explicit precondition ('Always read the record with list_cloudflare_dns_records and show the user exactly which record ... before calling') and names the sibling needed for discovery. It also flags the extra-confirmation case for records with managed_by 'external', so when-to-use and how-to-proceed are both covered.

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