unifi_gen_createfirewallpolicy

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

Annotations already declare that this is a non-read-only, open-world, non-idempotent, destructive mutation. The description adds no behavioral detail beyond the title, such as what policy scope is affected, what confirmation/preview behavior is exposed via the schema, or why a creation tool is marked destructive.

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?

The description is a single front-loaded sentence with no padding. It is concise, though the provenance phrase does not add much operational value.

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 firewall-policy creation tool with a nested vendor body, the definition is too sparse. The schema and annotations cover structure and safety hints, but the description does not explain usage context, sibling choice, or mutation consequences.

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 100%, so the schema already documents the body, confirm, and dry_run parameters. The description adds no parameter-specific meaning beyond pointing to the generated vendor source, so the baseline of 3 applies.

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: "Create Firewall Policy." It is clear what the tool does, but it does not distinguish this generated variant from the sibling unifi_net_create_firewall_policy tool or explain that they are duplicate/related creation paths.

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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives. An agent must infer that this is for creating rather than updating, patching, or deleting firewall policies, and must also infer which sibling create tool to use.

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