vsz_get_ap_radio

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

No annotations are provided, so the description carries the transparency burden. It clearly indicates a read operation ('Get', 'Returns') with no side effects disclosed, but does not cover error cases or authentication. This is adequate for a simple getter.

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 two sentences plus an Args list, front-loaded with the primary purpose and no filler.

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?

With an output schema present, the description sufficiently covers purpose, return section, and parameter semantics. It does not discuss error handling, but that is not essential for a simple read tool with a pre-defined output schema.

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 Args section adds meaning by defining 'host' as 'vSZ controller IP or hostname' and 'ap_mac' as 'AP MAC address', supplementing the empty schema descriptions. However, it lacks format validation details.

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 explicitly states 'Get radio configuration of an AP (2.4G / 5G / 6G)' and clarifies it returns the 'radioConfig section', which clearly defines the tool's purpose and distinguishes it from sibling tools like vsz_get_ap.

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 indicates it retrieves the radioConfig section, implying use when radio configuration is needed, but does not explicitly contrast with alternatives such as vsz_get_ap or vsz_get_ap_operational.

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