cmw_wlan_set_trigger

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

With no annotations, the description carries the full burden and does disclose key behaviors: the default source, threshold-crossing behavior, and timeout risk. It lacks explicit mention of immediate persistence or connection requirements, but the core behavioral context is well covered.

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?

Three sentences, front-loaded with the purpose, followed by behavior and a pointer to the catalog. Every sentence earns its place with no fluff.

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 setter, it covers the main source options, default, and timeout caveat. It doesn't elaborate on meas_instance or return values, but the schema covers the default and no output schema is needed. Overall adequate for the tool's complexity.

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%, with source and meas_instance described. The description adds meaning by comparing 'Free Run' and 'IF Power' beyond the schema's example. Host and port are generic and not described, but their purpose is self-evident and they are not required.

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 opens with a specific verb and resource: 'Set the WLAN measurement trigger source.' It clearly distinguishes this from sibling tools like cmw_wlan_trigger (which triggers a measurement) and cmw_wlan_trigger_catalog (which lists sources).

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?

It explicitly explains when to use 'Free Run' versus 'IF Power', warns about timeout behavior on infrequent bursts, and directs the user to cmw_wlan_trigger_catalog for supported sources. This gives actionable guidance beyond the schema.

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