Create WiFi broadcast

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

Annotations already flag destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is partially covered. The description adds nothing beyond that: it never says the tool previews by default until confirm=YES, that re-running creates a duplicate SSID, or what scope the new WLAN lands in -- all material for a destructive, non-idempotent create.

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?

Single short sentence, front-loaded and waste-free, but it is terse to the point of under-specification rather than genuinely concise. There is no second sentence earning its place because there is essentially no second sentence.

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, non-idempotent create with an undocumented-body payload and no output schema, the description omits the preview/confirm workflow and the payload's required fields. An agent reading only the description would not know that calling it without confirm=YES does nothing.

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 100% and confirm/dry_run carry clear descriptions, so the baseline of 3 applies. The description does not reinforce the critical two-step preview-then-apply pattern, which would have been the one place it could add value over the schema.

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?

States a specific verb and resource ('Creates a new WLAN'), but 'WLAN' is a different term from the title's 'WiFi broadcast' and the tool name's 'wifi', forcing the agent to reconcile terminology. Nothing distinguishes it from the near-identical sibling unifi_gen_createwifibroadcast.

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?

No indication of when to use this versus unifi_gen_createwifibroadcast or unifi_net_update_wifi, and no prerequisites (which site/network context, required payload shape) are given. The only usage nuance in play -- the confirm/dry_run preview path -- is left entirely to the schema.

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