unifi_create_firewall_group

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds minimal context by specifying 'new' (implying no overwrite) and 'IP or Port' (clarifying group type), but it does not mention permission requirements, duplicate name handling, idempotency, or what the response contains. This is insufficient for a create operation.

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 sentence with nine words, containing no filler or repetition. Every word earns its place, and the key information (action and group type) is front-loaded.

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 tool with 3 parameters, no annotations, and no output schema, the description is inadequate. It does not explain the group_type values, the structure of group_members, or any usage context. While it is not completely useless, it leaves too much uncertainty for an agent to invoke the tool correctly without additional knowledge.

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%, so the description must compensate. It hints that group_type distinguishes IP vs Port groups, which is useful, but it says nothing about the name parameter or the expected format of group_members (e.g., array of strings, CIDR notation, port ranges). This is a significant gap for a tool with only three parameters.

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 clearly states the action (create), the resource (firewall group), and the two possible group types (IP or Port). It distinguishes this tool from siblings like unifi_create_firewall_rule, which creates a rule rather than a group, and unifi_list_firewall_groups, which lists existing groups.

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 provides no guidance on when to use this tool versus creating a firewall rule, nor does it mention prerequisites or relationships with other firewall tools. It simply states what the tool does, leaving the agent to infer usage context from the tool name and siblings.

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