unifi_net_list_firewall_zonesList firewall zones on the current UniFi site, with filtering and pagination, to inspect zone-based firewall rules and verify network segmentation.
Lists all firewall zones on the current site.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| filter | No | ||
| offset | No |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered externally. The description adds only the site-scoping detail; it says nothing about pagination defaults, whether results are truncated at the limit, or the result shape, which matters for a list endpoint.
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?
A single front-loaded sentence with no filler or redundancy. It is efficient, but the brevity is achieved by omitting information rather than by selecting only the important information.
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?
No output schema exists, so the description should describe the returned collection or at least pagination semantics, and it does neither. For a paginated list tool with three undocumented parameters, the definition leaves the agent guessing at how to page through or narrow results.
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%: limit, offset and filter carry no documentation at all, and the description does not compensate. It never explains that limit caps at 200, that offset enables paging, or what filter syntax/fields are supported, leaving three parameters effectively opaque.
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 (lists firewall zones) and scopes it to the current site, which separates it from the singular unifi_net_get_firewall_zone. It does not acknowledge the parallel gen-style sibling (unifi_gen_getfirewallzones), so differentiation is implied rather than explicit.
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 the get/create/update/delete zone siblings or the gen-prefixed equivalents. The word "all" and the site scope hint at a bulk read, but the agent must infer everything else from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.