unifi_gen_getfirewallpolicyordering

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered structurally. The description adds only the 'User-Defined' scope qualifier and says nothing about what ordering data is returned, whether zones must be a valid pair, or what happens when no policies exist between the zones.

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, so it is not padded in length. However, the second half ('generated from developer.ui.com/...') is machine provenance that consumes space without informing the agent's decision, so not every element earns its place.

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?

With no output schema, the description is the only place that could explain the return shape — presumably an ordered list of policy IDs for the zone pair — and it says nothing about it. For a tool whose entire purpose is order, omitting how order is represented is a material gap.

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% and neither parameter has a description, so the description carries the burden of explaining sourceFirewallZoneId and destinationFirewallZoneId — including that both must be valid existing zone UUIDs and that the pair defines the ordering direction. It supplies none of that; only the self-evident property names carry meaning.

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 phrase 'Get User-Defined Firewall Policy Ordering' names a verb and a resource, so the basic operation is inferable. But it does not differentiate from the near-identical siblings unifi_net_get_firewall_policy_ordering and unifi_gen_updatefirewallpolicyordering, so an agent cannot tell which of the three to pick from the description alone.

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 statement of when to use this tool, no exclusions, and no pointer to the sibling that returns or mutates ordering. The only remaining sentence is a provenance note ('generated from developer.ui.com/...'), which is not usage guidance.

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