cmw_bt_fetch_power

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'fetch ... results', but doesn't mention side effects, required setup, whether results are reset, or any return format details. Minimal transparency.

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, front-loaded sentence with no unnecessary words. It immediately conveys the action and object, making it highly concise and scannable.

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?

Given the 3 parameters, no annotations, and no output schema, the description is too sparse to be contextually complete. It does not explain host/port, the meaning of meas_instance beyond a default, or how this relates to other Bluetooth tools. A more detailed description is needed for adequate completeness.

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 only 33% (only meas_instance has a description), and the description itself adds no parameter meaning. Host and port are left unexplained, and meas_instance is merely restated in the schema without elaboration. The description fails to compensate for the low 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 clearly states a specific verb and resource: 'Fetch Bluetooth TX power measurement results'. It distinguishes from siblings like cmw_bt_fetch_modulation and cmw_bt_fetch_frequency by specifying the exact measurement type.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., prior configuration/trigger) or differentiation from cmw_meas_fetch_power, which also fetches power results.

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