delete_firewall_zone_proxy

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It conveys that the operation deletes a resource, but fails to mention irreversibility, potential side effects, permissions needed, or failure conditions. This is a destructive operation, so more behavioral disclosure is warranted.

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?

The description is compact, front-loaded with the purpose, and uses a clear parameter breakdown. Every sentence adds value, and there is no redundant or verbose 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?

All required parameters are covered and the provenance of zone_id is explained; the presence of an output schema reduces the need to document return values. The description is complete enough for making the call, though a brief note on the destructive/permanent nature would strengthen it.

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%, and the description fully compensates by explaining each parameter: host accepts console name, ID, or composite ID (MAC:numericId format), site accepts name or ID, and zone_id is required and sourced from list_firewall_zones_proxy. This provides meaningful guidance beyond the raw schema.

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 specific action ('Delete a firewall zone') and the mechanism ('via connector proxy'), which clearly distinguishes it from sibling tools like list, get, or update firewall zone proxy. The resource and operation are 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?

The description clearly instructs that zone_id is required and must be obtained from list_firewall_zones_proxy, providing an explicit prerequisite and source. It does not explicitly state when not to use this tool versus alternatives, but the delete-focused context makes the use case clear.

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