cmw_bt_set_ble_mode

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the operation is a 'Set' action, without explaining side effects, persistence, prerequisites, or whether it targets a specific measurement instance. The parenthetical mode list adds detail but not behavioral context.

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 front-loads the action and includes the key mode alternatives. Every word adds value with no 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 4 parameters, no output schema, and no annotations, the description is minimal. It omits context about targeting an instrument (host/port) and selecting a measurement instance, which are essential for effective invocation. The description only addresses the ble_mode parameter, leaving the other parameters under-explained.

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 description coverage is 50% (host and port lack descriptions). The description adds a plain-language mapping for ble_mode (1M, 2M, Coded S2/S8) but does not explain host, port, or meas_instance. It partially compensates for the schema gaps but not fully.

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 action 'Set BLE PHY mode' and specifies the allowed values (1M, 2M, Coded S2/S8). This distinguishes it from sibling tools like cmw_bt_set_frequency or cmw_bt_set_packet_type, which target different aspects of BLE configuration.

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 usage is implied by the name and description: use when you need to configure BLE PHY mode. However, there is no explicit guidance on prerequisites, when it should be used relative to other BT setup commands, or alternatives. The description does not mention connection requirements or the need to set other parameters first.

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