Delete a zone ruleset

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description still earns credit for disclosing that the deletion spans ALL versions of the ruleset (not just the active one) and for the practical retry rule about not repeating an unknown outcome — exactly the ambiguity an agent faces with a non-idempotent destructive call. It stops short of stating permission requirements or blast radius on dependent resources.

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 short sentences, zero filler, and the destructive scope is front-loaded before the safety guidance. Every sentence carries actionable content.

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 delete with no output schema, the definition covers what is destroyed and how to behave on ambiguous outcomes, and annotations carry the safety metadata. It is slightly thin on prerequisites (which token/permission is needed) and on the fact that only ruleset_id is required while zone_id/account are optional routing inputs.

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?

The description never references any of the five parameters; confirm and dry_run are documented only in the schema. With 60% schema coverage and the $defs supplying ID descriptions for zone_id/ruleset_id, the schema does the heavy lifting, so the baseline of 3 applies — the description adds no syntax, format, or constraint detail.

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 ("Deletes ... an existing zone ruleset") and adds scope precision with "all versions," which distinguishes it from a hypothetical single-version delete. It does not name or contrast any sibling such as update_zone_ruleset or delete_dns_record, so an agent must infer the routing from the name alone.

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?

"Every change requires explicit confirmation" gives an invocation precondition, and the retry caution implies this is not something to fire speculatively. However, there is no statement of when this tool is the right choice versus update_zone_ruleset or list_zone_rulesets, and no exclusion guidance — usage is only implied.

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