unifi_create_network

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 only states 'Create a new network subnet / VLAN' with no details on side effects, idempotency, permissions, or potential conflicts (e.g., duplicate subnets). This is effectively a tautology of the tool name.

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 short sentence, but it is under-specified rather than concise. It lacks any structure or additional detail, making it insufficient for a create operation with multiple parameters. Conciseness should not come at the cost of necessary information.

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?

The tool has 4 parameters, 2 required, no annotations, no output schema, and no parameter descriptions. The description only covers the basic action, omitting required parameters, input formats, expected behavior, and return values. It is critically incomplete for an agent to invoke correctly.

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 coverage is 0% and the description does not explain any of the four parameters (name, ip_subnet, vlan, purpose). The phrase 'subnet / VLAN' hints at ip_subnet and vlan but provides no format, constraints, or relationships between parameters, leaving the agent to guess.

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 'Create a new network subnet / VLAN' uses a specific verb and resource, clearly indicating a create operation for network subnets/VLANs. It distinguishes from sibling update/delete/list tools, though it does not explicitly contrast with create_wlan for wireless networks.

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 alternatives like create_wlan or update_network. No context, prerequisites, or exclusions are provided, leaving the agent to infer usage.

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