unifi_gen_getfirewallpolicies

Does 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 covered structurally. The description adds nothing behavioral beyond a source-doc citation — no mention of pagination behavior, default page size, result ordering, or how the open-world 'filter' query is applied.

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?

It is short and front-loaded, which is good, but half the content is a 'generated from developer.ui.com/...' provenance note that provides no value to an invoking agent. The brevity here reflects under-specification rather than disciplined concision.

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?

Placeholder check: this dimension is scored on the definition as a whole. With a read-only list tool, annotations covering safety, no output schema required, and no required parameters, an agent can invoke it correctly with a bare call; the missing filter grammar is the main residual gap and is penalized under parameter_semantics.

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%, so all three parameters (limit, offset, filter) are undocumented anywhere. The description makes no attempt to explain them, and 'filter' in particular has an unknown syntax/grammar that an agent cannot infer from the schema alone.

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 gives a clear verb+resource ('List Firewall Policies'), which is enough for an agent to know it enumerates the collection rather than fetching one policy like unifi_gen_getfirewallpolicy. It does not, however, distinguish itself from the near-identical sibling unifi_net_list_firewall_policies, nor does it state scope (site-level? all sites?).

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 when-to-use guidance, no mention of when to prefer this over unifi_net_list_firewall_policies, and no note about pagination or prerequisites. The only usage-adjacent text is a documentation URL, which is not actionable guidance for tool selection.

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