cloudflare_delete

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

With no annotations, the description carries the full behavioral burden. It usefully discloses a safety gate ('confirm must equal record_id'), giving real context beyond the schema's bare string type, but omits permission requirements, reversibility, and error/failure behavior expected of a destructive operation.

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 compact sentences, front-loaded with the action and immediately followed by the one constraint that matters. 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 tool with no annotations and no output schema, the confirmation protocol is the key missing piece the description supplies. Still, permission/auth requirements and what a successful deletion returns are absent, so an agent lacks a full operational picture.

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 0%, so the description must compensate for all three parameters. It explains the semantics of 'confirm' (must equal record_id) but says nothing about zone_id or record_id beyond their self-evident names, so coverage is partial.

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 ('Delete') and resource ('A/AAAA/CNAME record'), which distinguishes it from cloudflare_upsert and cloudflare_records at a glance. It does not explicitly name a sibling, but the destructive scope is unambiguous.

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 authorized' implies a precondition for use, hinting the agent must confirm the record is sanctioned before deleting. However, it never states when to prefer this over cloudflare_upsert or how authorization is established, leaving usage largely inferred.

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