unifi_gen_createwifibroadcast

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no note about what a failed create leaves behind, whether duplicate SSIDs are allowed, or what the confirm/dry_run preview returns.

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?

It is a single short line with no bloat, but half of it is a vendor-docs URL rather than usable guidance. Brevity here reflects under-specification rather than disciplined editing.

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?

This is a destructive create with a 25+ field body schema full of opaque nested objects (securityConfiguration, multicastFilteringPolicy, hotspotConfiguration) typed only as free-form objects, and no output schema. The description supplies only a link, leaving the agent without the field-level context the schema cannot provide.

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 100%, so the body, confirm and dry_run parameters are already documented in the schema. The description contributes no extra semantics, which meets the baseline of 3 when the schema does the work.

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?

"Create Wifi Broadcast" restates the tool name (unifi_gen_createwifibroadcast) almost verbatim, so it is close to tautological. It does not differentiate from the near-identical sibling unifi_net_create_wifi or from unifi_gen_updatewifibroadcast, and the only added content is a provenance URL.

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 when-to-use guidance is given. With both unifi_net_create_wifi and unifi_gen_createwifibroadcast in the sibling list, an agent has no stated rule for choosing one, and no prerequisites or constraints are mentioned.

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