cmw_bt_fetch_all

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 what data is fetched, but does not disclose whether measurement must be triggered first, whether results are cached, what happens if no measurement data exists, or any side effects. The description is minimal and does not provide meaningful behavioral context beyond the basic action.

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 core purpose. It is appropriately sized for a simple fetch tool, though it omits potentially useful context. No word is wasted, but the brevity becomes a drawback in other dimensions.

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 lack of output schema, annotations, and the presence of sibling tools that provide detailed measurement fetches, the description is incomplete. It does not explain return value structure, prerequisites for calling this tool, or how errors are handled. The tool appears to aggregate multiple measurements, but the description does not elaborate on the combined result format.

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 description coverage is only 33%, with host and port lacking any description. The tool description does not compensate for this, providing no details about what host and port refer to or how meas_instance is used. The description adds no parameter semantics beyond what the schema already offers.

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 tool fetches all Bluetooth measurement results and explicitly enumerates the types (power, modulation, frequency). This distinguishes it from sibling tools like cmw_bt_fetch_power, which only fetch individual measurement types.

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 implies usage context by mentioning 'all' results, which contrasts with sibling tools for individual measurements. However, it does not explicitly state when to prefer this tool over the individual fetch functions, nor does it mention any prerequisites or conditions. Usage guidance is implied but not explicit.

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