Create firewall zone

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it doesn't say what a zone creation affects, whether duplicate names are rejected, or that omitting confirm yields a preview rather than a write — that last point only appears in the schema.

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?

Two short sentences with no wasted words and the operation front-loaded, but the brevity reflects under-specification rather than disciplined concision, and the pointer to external docs is a weak substitute for content.

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 destructive, non-idempotent mutation with an opaque body and no output schema, the description leaves too much unsaid: no payload field guidance, no preview/confirmation workflow, no note on what is returned or what side effects follow.

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?

Coverage is nominally 100%, but the most important parameter, 'body', has no type and no properties — only 'Firewall zone create payload' — and the description merely defers to external 'Firewall API docs' an agent may not have. The confirm/dry_run semantics are already fully spelled out in the schema, so the description contributes no additional parameter 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?

States a specific verb and resource ('Creates a new firewall zone') and adds the scoping detail 'on the current site'. It does not differentiate from near-duplicate siblings such as unifi_gen_createfirewallzone or explain the relationship to unifi_net_create_firewall_policy.

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?

No when-to-use or when-not-to-use guidance, no prerequisites (e.g. whether zones must exist before policies reference them), and no mention of the confirm/dry_run workflow in prose. The agent must infer everything from the schema.

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