Get WiFi broadcast

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

Annotations already declare readOnly, idempotent, non-destructive, open-world semantics, so the safety profile is covered. The description adds no behavioral context of its own — not what fields the 'detail' includes, not what happens when the id is unknown or invalid.

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?

Four words is concise but under-specified rather than efficient; there is no front-loaded statement of object or identifier format. It reads as a placeholder rather than a deliberate minimum.

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?

No output schema, zero parameter documentation, and no hint of the returned payload. For a get-by-id tool whose only required argument is unexplained, the description leaves the agent unable to call it correctly with confidence.

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% and the single required parameter 'id' is completely undocumented in both schema and description. The agent cannot tell whether 'id' is a WLAN id, a network id, an SSID name, or a UUID — the description must compensate here and does not.

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?

"Detail for a WLAN" gestures at retrieval of a single WLAN object, but 'Detail' is a noun phrase with no explicit verb and 'WLAN' is never tied to 'WiFi broadcast' from the title. It does not distinguish this from the many sibling list/get tools such as unifi_net_list_wifi or unifi_gen_getwifibroadcastdetails.

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 statement of when to use this versus unifi_net_list_wifi (list) or other get-by-id siblings. The only faint signal is the word 'Detail', which implies a single-record fetch, but nothing is explicit.

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