vsz_get_wlan_statistics

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

With no annotations provided, the description carries the behavioral disclosure burden. It explains that the tool uses the query API, the type of statistics returned, and that omitting `wlan_name` returns all WLANs. This provides meaningful behavioral context beyond the schema, though it does not cover authentication or potential performance limitations.

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 compact and well-structured. It leads with the tool's purpose, then summarizes the output and lists arguments with clear, concise explanations. Every sentence contributes useful information without redundancy.

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 tool with two parameters and an output schema, the description covers the essential purpose, parameter semantics, and behavior. It lacks explicit guidance on when to choose this tool over siblings, but this is a minor gap for a simple getter and the output schema covers return value details.

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 schema descriptions for parameters are minimal ('Host', 'Wlan Name'), so the description adds essential meaning. It specifies that `host` expects an IP or hostname and that `wlan_name` is an optional filter defaulting to all WLANs. This fully compensates for the lack of schema-level descriptions.

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 clearly states the tool's function: 'Get statistics for WLANs via the query API.' It enumerates the returned statistics (client count, traffic, status), which distinguishes it from sibling tools like `vsz_list_wlans` and `vsz_get_wlan` that focus on WLAN configuration rather than statistics.

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 clear context for when to use the tool: when WLAN statistics are needed, with an optional filter by WLAN name. However, it does not explicitly name alternative tools or state when not to use it, stopping short of full usage guidance.

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