cmw_wlan_set_frequency

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the action 'Set' and provides no context about side effects, required prior setup, valid frequency ranges, or whether the change is reversible. For a mutation tool, this is a significant gap.

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, concise sentence that immediately conveys the core action. It contains no filler or redundant elaboration, making it appropriately sized and front-loaded.

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 four parameters and no output schema, the description is too sparse to fully contextualize the operation. It does not explain whether this sets the RF carrier frequency for WLAN measurement, whether it depends on other settings like standard or bandwidth, or what the tool returns after execution. The complexity of the domain and sibling toolset demands more.

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 coverage is 50%, but the description adds no meaning for the undocumented 'host' and 'port' parameters. It merely restates the unit 'Hz' that already appears in the frequency_hz parameter description, and does not clarify the semantics of 'measurement frequency' or the role of meas_instance.

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 'Set WLAN measurement frequency in Hz' uses a specific verb ('Set'), specifies the resource ('WLAN measurement frequency'), and includes the unit. It is clear and distinguishes from siblings like cmw_meas_set_frequency by the WLAN qualifier.

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 guidance on when to use this tool versus alternatives such as cmw_meas_set_frequency or cmw_gen_set_frequency. It does not mention prerequisites, exclusions, or that it is the WLAN-specific configuration path.

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