unifi_gen_getfirewallpolicy

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing behavioral beyond a documentation-source URL — no error behavior for an unknown ID, no return shape, no auth notes.

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?

Extremely short and front-loaded with the action. The trailing "generated from developer.ui.com/..." provenance string is metadata noise rather than useful guidance, keeping it out of the top score.

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 single-parameter lookup with no output schema, the description should at least say what is returned or how to source the ID. With annotations carrying the safety profile, the remaining burden on the description is modest but still unmet.

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 single parameter firewallPolicyId has 0% schema description coverage; the schema supplies only type/format/pattern. The description never explains that the value is a policy UUID or where to obtain one, 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?

The description names a specific verb and resource ("Get Firewall Policy"), so the basic action is clear, and the singular form hints at a single-record fetch versus the sibling list tool. However, it offers no differentiation from the near-duplicate sibling unifi_net_get_firewall_policy, and the only other content is a provenance URL.

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 tool versus unifi_gen_getfirewallpolicies or unifi_net_get_firewall_policy, and no stated prerequisite such as needing an ID obtained from a list call. Usage must be inferred entirely from the name.

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