network_create_wifi

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states 'Create a new WiFi broadcast' without mentioning mutation implications, permission requirements, side effects (e.g., overwriting existing SSID), or any constraints. Critical behavioral traits are missing.

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 short and front-loaded with the purpose, followed by a simple 'Args' section. It is concise and avoids unnecessary words, though it could benefit from more structured formatting (e.g., bullet points for clarity).

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?

Given the existence of an output schema, the description does not need to detail return values. However, for a creation tool with a complex nested parameter, it lacks essential details like required fields within the data object, validation rules, or how to construct the configuration. The description is minimally complete.

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 adds minimal value: 'site_id: The site ID' and 'data: WiFi configuration (name, security, etc.)'. While it provides some context, the data parameter is vague for a complex object with additionalProperties. More precise field descriptions are needed.

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 'Create a new WiFi broadcast (SSID) on a local UniFi site', which specifies the verb (create), resource (WiFi broadcast/SSID), and context (local UniFi site). This effectively distinguishes it from sibling tools like network_update_wifi and network_delete_wifi.

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 alternatives like network_create_network or network_update_wifi. It lacks any 'when-to-use' or 'when-not-to-use' information, making it difficult for an agent to choose correctly among siblings.

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