Delete Cloudflare Record

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

Annotations already flag destructive and non-readOnly, but the description adds real context beyond them: live DNS impact, the risk of taking a site or its mail offline, the confirmation requirement, the read-before-delete behavior that makes the response authoritative, and dry_run support.

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?

Four tight sentences with the destructive warning front-loaded and no wasted clauses; every sentence carries operational information.

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?

No output schema exists, and the description compensates by explaining that the response reports exactly what was removed, plus confirmation and dry_run behavior — everything needed to call this destructive tool safely.

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 67% and dry_run has no schema description, so the description's 'Supports dry_run' supplies the missing meaning. The record_id provenance is echoed from the schema but reinforced with the sibling tool name.

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 from a domain's Cloudflare zone') and scopes it to Cloudflare-authoritative zones, which distinguishes it from the sibling delete_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 clear preconditions ('confirm with the user first') and routes the agent to get_cloudflare_records for the record_id. It does not, however, state when to prefer this over the sibling delete_dns_record, so the alternative selection is left implicit.

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