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

With only destructiveHint=true available, the description adds real behavioral context the annotation cannot convey: the blast radius (affects every instance, cluster, and load balancer on the firewall) and reversibility (no API undo — must be deleted via dashboard or CLI). That is exactly the 'what gets destroyed / how to undo' information an agent needs before mutating.

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 short sentences, front-loaded with purpose, then impact, then undo path, then the API mapping. Nothing is padded and the most important warning (blast radius) appears early.

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, no-output-schema mutation tool, the description covers purpose, example, blast radius, and reversal path, while region and enum semantics are fully handled by the schema. Nothing needed to call it correctly 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 100%, so the baseline is 3. The description climbs above it by illustrating the interaction of protocol/port/direction/cidr in one example and reinforcing CIDR semantics ('prefer narrow CIDRs'), which adds practical meaning beyond the field definitions.

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 (Add) and resource (one rule to a firewall) and immediately grounds it with a concrete example ('allow TCP 443 ingress from 0.0.0.0/0'). An agent can distinguish this from civo_list_firewall_rules and civo_list_firewalls without consulting any schema.

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 operational context ('changes what is reachable on every instance, cluster and load balancer', 'prefer narrow CIDRs'), which tells the agent when care is warranted. It does not, however, name an alternative tool or state explicit exclusions, so it stops short of the when-not/alternatives bar.

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