cmw_bt_fetch_frequency

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 merely states 'Fetch' without mentioning prerequisites (e.g., connection/configuration required), whether a measurement must be triggered first, or what happens if no results exist. No behavioral traits are exposed 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 is front-loaded with the verb and resource. It is efficient and easy to parse, though it lacks any additional explanatory structure. This is appropriately sized for the small amount of information conveyed.

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?

There is no output schema, no annotations, and only minimal schema descriptions. For a measurement fetch tool, the description should explain return values or preconditions, but it only gives a terse statement. Compared to siblings with richer descriptions, this one is incomplete for guiding proper use.

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 only 33% (only meas_instance has a description). The description adds no meaning for host or port, failing to compensate for the low coverage. It does not explain how these parameters are used or their relationships, leaving the agent guessing.

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's verb ('Fetch') and resource ('Bluetooth frequency measurement results'), which is specific and distinguishes it from sibling tools like cmw_bt_fetch_power or cmw_bt_fetch_modulation. It directly communicates what the tool does without ambiguity.

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, such as cmw_bt_fetch_all or cmw_meas_fetch_frequency. The description lacks any contextual cues or exclusions, leaving the agent without direction on selecting this tool appropriately.

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