Delete a firewall

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

With no annotations, the description carries the full burden, and it does disclose the two most important traits: the operation is destructive and is gated behind confirm true, plus the cost angle ('free'). It omits irreversibility, permission requirements, and side effects on servers referencing the firewall.

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 terse sentences with the action front-loaded and zero filler; the destructive/confirmation constraints follow immediately. Nothing is padded.

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 mutation tool with no annotations and no output schema, the essential invocation facts (destructive, confirm gate, free) are present, but reversibility, resulting state, and any impact on dependent resources are unaddressed.

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 exactly 50% – id is documented in the schema, but confirm has no schema description. The description compensates by specifying that confirm must be true, resolving the undocumented parameter's required value.

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?

The description states a clear verb and resource ('Delete a firewall'), matching the title and distinguishing it from siblings like cloud_create_firewall and cloud_list_firewalls by operation type. It does not, however, explicitly differentiate itself from other delete tools or call out the sibling relationship.

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?

It states the invocation requirement (confirm true) but gives no when-to-use guidance, no exclusions, and no reference to alternatives such as cloud_list_firewalls for verifying the target first. An agent learns how to call it, not when it should.

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