cmw_bt_set_expected_power

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Set', implying a mutation, but does not disclose side effects, required setup, whether the value persists, or what happens if the instrument is not in the right state. This is a significant gap for a state-changing tool.

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, front-loaded sentence that directly states the action and target. It contains no redundant or extraneous words.

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?

Despite having 4 parameters, no output schema, and no annotations, the description provides minimal context. It does not clarify the role of host, port, meas_instance, or the expected behavior or side effects. An agent would lack enough guidance to use this tool correctly in a larger workflow.

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 schema already describes 'power_dbm' as 'Expected power in dBm', so the description's 'in dBm' adds no new meaning. Host, port, and meas_instance semantics are not explained in the description, and schema coverage is only 50%, leaving those parameters under-documented.

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 a specific action ('Set'), a specific resource ('Bluetooth expected input power'), and the unit ('in dBm'). This distinguishes it from sibling tools like cmw_wlan_set_expected_power or cmw_meas_set_expected_power by naming the Bluetooth context.

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 gives no guidance on when to use this tool versus alternatives, such as cmw_meas_set_expected_power or cmw_wlan_set_expected_power. It also does not mention prerequisites like configuring Bluetooth measurement or making a connection.

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