unifi_list_firewall_rules

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

No annotations are provided, so the description must disclose behavior. It communicates that the operation is a read-only list and specifies key output fields, but it does not mention pagination, required privileges, or any edge cases. The verb 'List' provides some basis for assuming no side effects, but deeper behavioral context is lacking.

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 a single concise sentence with no filler, front-loading the core action and then adding relevant detail about the output. It is efficiently written and easy to scan.

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 simple list operation with no parameters, the description covers the main purpose and identifies the key return fields. However, without an output schema, it only lists three fields and does not mention whether additional fields exist or whether pagination is involved, leaving some ambiguity.

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?

The tool has zero parameters, so the schema already fully covers inputs. The description adds value by describing output contents, which is helpful given no output schema, but no parameter-level semantics are needed.

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 clearly states 'List configured firewall rules' with a specific verb and resource, and elaborates on the returned fields (rule numbers, action, interface bindings). It distinguishes from siblings like unifi_list_firewall_groups by focusing on firewall rules, not groups.

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 implies usage (when you need to view firewall rules) but does not explicitly state when to prefer this over alternatives such as unifi_list_firewall_groups or unifi_list_port_forwards. There is no mention of exclusions or prerequisites, so guidance is only implied.

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