unifi_gen_updatefirewallzone

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the description need not re-establish the safety profile — but it adds nothing about what a destructive update actually replaces (e.g., whether networkIds is overwritten wholesale), nor about permission or preview behavior. Only a raw source URL is supplied. No contradiction with annotations, but no added value either.

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 text is short and front-loaded with the verb and resource, so nothing is bloated. However, the second half is a bare documentation URL, which is filler relative to the missing operational content, and the overall size is under-specified rather than efficient.

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 a loosely typed anyOf body and no output schema, the description should explain what changes, whether the body replaces or merges existing zone fields, and how the preview/confirm path works. None of that is present, and the duplicate-vendor sibling is not disambiguated.

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 75%, just under the threshold where a baseline 3 is granted for the schema doing the work. The description supplies no parameter meaning at all — notably nothing about firewallZoneId (which lacks a schema description) or the confirm/dry_run preview contract — so it fails to compensate for the coverage gap.

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?

"Update Firewall Zone" restates the tool name and title verbatim, adding only a vendor-docs URL. It does name a verb and a resource, but there is no scope, no statement of what aspects of the zone are updated, and no differentiation from the sibling unifi_net_update_firewall_zone / unifi_gen_createfirewallzone / unifi_gen_deletefirewallzone.

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?

No when-to-use, prerequisites, or alternatives are stated. In particular the description gives no help choosing between this tool and unifi_net_update_firewall_zone, which appears to target the same resource, nor when to use update vs. create/delete for zones.

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