cmw_wlan_set_repetition

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

With no annotations, the description carries the full burden. It discloses a key behavioral trait: CONTinuous mode never reports a finished state, which is critical for understanding measurement synchronization. It also states the default behavior. This goes beyond a simple setter description and alerts the agent to a subtle consequence.

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 sentences, front-loaded with the action, followed by crucial contextual detail. No redundant or filler content. Every sentence earns its place and the description is easy to parse quickly.

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 tool with no output schema and basic annotations, the description is nearly complete. It explains the core setting, the default, and the main gotcha (CONTinuous never finishes). It does not mention prerequisites like prior WLAN configuration, but this is likely implied by the tool suite and not necessary for basic invocation.

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 description adds meaning to the 'repetition' parameter by explaining the default and the practical implication of each mode, which the schema only hints at with 'SINGleshot for a synchronised measurement'. It does not cover host/port, but those are standard connection parameters. The added context for the key parameter compensates for the 50% schema coverage.

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 uses a specific verb+resource combination: 'Set WLAN repetition' and explicitly lists the two possible values (SINGleshot or CONTinuous). This clearly distinguishes the tool from sibling tools like cmw_wlan_set_trigger or cmw_wlan_set_frequency, which handle different settings.

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 on when to use each value: it states the default is CONTinuous and that a synchronised measurement requires SINGleshot. This is practical guidance for choosing the correct parameter, though it does not explicitly mention alternatives or when not to use this tool (e.g., other configuration steps).

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