unifi_gen_deletefirewallzone

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond a source URL — it doesn't mention the confirm/dry_run preview flow, irreversibility, or what happens to referencing policies.

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?

Very short and front-loads the action, but the trailing "generated from developer.ui.com/..." provenance clause consumes roughly half the text without helping an agent decide or invoke.

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, open-world mutation with no output schema and an ambiguous duplicate sibling, the description should cover the preview/confirm workflow and ambiguity with unifi_net_delete_firewall_zone. It covers neither.

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 a middling 67%, and the description explains none of the three parameters. The confirm="YES" preview gate and dry_run semantics are documented only in the schema, and firewallZoneId has no description at all in either place.

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 Custom Firewall Zone"), which is clearly a destructive counterpart to get/create/update firewall zone siblings. It does not differentiate from the near-duplicate sibling unifi_net_delete_firewall_zone or explain what a "Custom" zone is.

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 guidance on when to use this versus unifi_net_delete_firewall_zone, no prerequisites, and no warning about dependencies such as attached firewall policies. The only usage-relevant text is a provenance URL.

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