unifi_gen_updatefirewallpolicy

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the risk profile is conveyed structurally. The description adds nothing beyond that — no note that this is a full replacement of the policy body, no confirmation flow explanation, no permission requirements. It neither contradicts nor enriches the annotations.

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 a single short sentence with the operation front-loaded, so it is not padded. However the brevity comes from omission rather than efficiency — the second half is a raw docs URL rather than information an agent can act on.

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?

This is a destructive update against a complex nested body object with required fields (action, source, destination, ipProtocolScope) whose sub-schemas have no property descriptions, and there is no output schema. The description does not explain replacement semantics, the preview/confirm gate, or what the response contains — a serious gap for an unannotated-body mutation.

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 75%, with the schema itself documenting body, confirm ("YES" to apply, otherwise preview) and dry_run. The description contributes no parameter meaning and does not explain that firewallPolicyId identifies the target policy or that body must be the complete vendor payload. Baseline 3 is appropriate given the schema carries most of the weight.

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 states a specific verb and resource ("Update Firewall Policy") plus a docs URL, so an agent knows this modifies an existing firewall policy. But it does not differentiate from near-identical siblings such as unifi_gen_patchfirewallpolicy or unifi_net_update_firewall_policy, which is where the real ambiguity lies. Effectively it restates the tool name with a provenance link.

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, when-not-to-use, or alternative guidance at all. The sibling list contains both a patch variant and a differently-named update variant, and the description gives the agent nothing to choose among them. Only the name implies the operation.

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