unifi_list_wlans

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

With no annotations provided, the description must carry the full burden. The verb 'List' implies a read operation, and the returned fields are listed. However, it does not explicitly state that no modifications occur, nor does it mention authentication requirements, rate limits, or sensitivity of passphrases.

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 a single, front-loaded sentence that states the action and the specific data returned. Every word contributes value, with no redundancy or extraneous information.

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 that there is no output schema, the description lists the key WLAN attributes, serving as a partial output contract. It does not clarify whether 'all' means all sites or just the current site, nor does it mention pagination or error behavior, but for a simple list tool it is largely sufficient.

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?

The tool has zero parameters and an empty schema. Since there are no parameters to describe, the description does not need to add parameter details. According to the rubric, a zero-parameter tool receives a baseline score of 4.

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 uses the specific verb 'List' and clearly identifies the resource as configured Wi-Fi SSIDs, enumerating distinct attributes (passphrases, security modes, frequency bands, enabled status). This distinguishes it from sibling tools that create, update, delete, or set WLAN properties.

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 explicit guidance on when to use this tool versus alternatives. It does not mention that it is a read-only operation or point to alternatives like unifi_list_networks or unifi_get_health. Usage is only implied by the resource name and action.

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