unifi_create_wlan

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

No annotations provided, so description carries full burden. Only mentions creation and conditional parameter constraints; lacks details on idempotency, authorization needs, duplicate handling, or success response.

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?

Very concise, front-loads main action, no unnecessary words. Every sentence adds 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?

With 11 parameters, 0% schema coverage, no annotations, and no output schema, the description leaves gaps: no success indicators, error conditions, or prerequisites for optional IDs. Incomplete for a complex creation tool.

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?

Covers 6 of 11 parameters (security, passphrase, wlan_band, vlan_id, is_guest, name implied). Adds conditional logic and enum descriptions but omits site_id, enabled, hide_ssid, usergroup_id, networkconf_id. Schema coverage 0% so description partially compensates.

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?

Clearly states 'Create a new WLAN (SSID).' Verb+resource is specific and distinguishes from sibling tools like update, delete, list.

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?

Implied usage from tool name and description, but no explicit when-to-use or when-not-to-use instructions relative to siblings. Some conditional parameter guidance is given but not usage context.

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