cvcue_list_ssids

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

No annotations are supplied, so the description carries the full burden; it does disclose the returned fields, which is the most useful behavioral detail here. It is silent on ordering, pagination/result limits, and permission requirements, and 'List' only implicitly signals a read-only, non-destructive operation.

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?

Two sentences, zero waste: the payload of returned fields is front-loaded and the alternative-tool pointer comes second. Nothing repeats the tool name or restates the schema.

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 simple read-only list tool with two optional, fully documented parameters, the description covers purpose, return shape, and the detailed alternative. Minor gaps remain around result volume and location scoping behavior, but nothing an agent needs to invoke it correctly is missing.

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 location_id and include_subtree are already documented, and the phrase 'where the profile was created' only loosely gestures at location scoping. The description adds no syntax, defaults, or subtree semantics beyond the schema, so the baseline 3 applies.

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 ('List SSID profiles (WLANs)') and enumerates exactly what is returned — name, enabled, VLAN, security mode, guest, client isolation, creation location. This distinguishes it cleanly from cvcue_get_ssid, which is named as the detailed counterpart.

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?

Explicitly routes the agent to cvcue_get_ssid when the full configuration is needed, which is a clear use-vs-alternative condition. It does not address the other SSID-adjacent siblings such as cvcue_ssid_usage or the write-side tools, so the routing is clear but not exhaustive.

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