cf_dns_delete

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

With no annotations, the description carries the full burden for a destructive operation. '(gated)' hints at a safeguard but never defines it, and nothing is said about irreversibility, permissions, or the role of the confirm flag. The one behavioral hint is too vague to act on.

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?

A single short, front-loaded sentence with no wasted words. The parenthetical is the only element that fails to earn its place by being unexplained.

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 3-parameter tool with no annotations, no output schema, and zero schema documentation, the description is far too thin. At minimum it should define 'gated'/confirm semantics and the required zone scoping.

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 0% across 3 parameters, so the description must compensate and largely does not: it mentions only 'id' and says nothing about 'zone' or the 'confirm' boolean. The '(gated)' aside loosely gestures at confirm but never explains its meaning or default.

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 the lookup key ('by id'), which cleanly separates it from cf_dns_create and cf_dns_update. The parenthetical '(gated)' is cryptic and adds no clarity, and there is no explicit naming of siblings.

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?

There is no when-to-use guidance, no mention of prerequisites or alternatives, and no explanation of what 'gated' means in practice. An agent gets no help deciding between this and cf_dns_update or cf_purge_cache.

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