Delete Cloudflare Record

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds real value on top: this mutates live authoritative DNS, can take a site or mail offline, should be user-confirmed, is read-before-delete so the response reports the removed record, and supports dry_run. That is exactly the extra behavioral context the annotations cannot convey.

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 and risk, then prerequisites, then the read-before-delete and dry_run notes. Every sentence carries operational information with no filler.

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, open-world mutation with no output schema, the description covers the danger, the confirmation requirement, the id source, and what the response will contain. Nothing essential for correct invocation is missing.

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%: domain and record_id are described in the schema, and the description usefully reinforces record_id's source. dry_run is only mentioned as supported without explaining what it does, and domain gets no additional detail, so it adds modest value beyond the schema.

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 Cloudflare zone) and scopes it to zones Cloudflare is authoritative for, which separates it from the generic delete_dns_record sibling. An agent can identify the operation and its blast radius immediately.

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?

Explicitly instructs confirming with the user first and tells where to obtain record_id (get_cloudflare_records), which is strong usage context. It does not explicitly contrast with delete_dns_record or edit_cloudflare_record, so the sibling routing is implied rather than stated.

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