getSsidList

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

With no annotations, the description is the only behavioral signal. It clearly implies a read operation via 'Get the list,' but it does not state authorization needs, pagination, error behavior, or response structure beyond the presence of ssidId. The behavior is mostly implicit.

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 short sentences with no filler. The core purpose is front-loaded, and the second sentence adds only actionable prerequisite and successor 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?

The description forms a coherent chain: obtain wlanId, get SSID list, then call getSsidDetail with ssidId. It omits return-format details and siteId semantics, which is a small gap for a simple getter, especially given no output schema or annotations.

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%, so the description must compensate. It explains wlanId's provenance and that ssidId is usable downstream, but it leaves the optional siteId completely unexplained and does not describe wlanId's format or meaning beyond its source.

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: 'Get the list of SSIDs configured in a WLAN group.' The follow-up instruction to use the ssidId for getSsidDetail differentiates it from the detail sibling, making its role clear.

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?

Provides explicit workflow context: wlanId comes from getWlanGroupList, and the resulting ssidId feeds getSsidDetail. This is clear guidance for when to call it, though it does not mention exclusions or cases where another list tool would be preferable.

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