cmw_set_band

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

The description only states the function without any behavioral details such as side effects, prerequisites, or state changes. Annotations only indicate non-destructive, but no further context is provided.

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 very short but lacks necessary details. The '[CMW]' prefix adds little value, and the remaining text could be more structured to include parameter or usage info.

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 an output schema, the description fails to explain parameters or provide usage guidance, leaving it incomplete for effective 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?

The schema has no descriptions for parameters (0% coverage), and the description does not explain the meaning or usage of 'alias' and 'params_json'. The examples given are about band values, not parameters.

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 that the tool sets LTE bands and provides specific examples (OB1, OB3, etc.), distinguishing it from siblings like cmw_set_bandwidth and cmw_set_dl_channel.

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 for setting LTE bands, but provides no explicit guidance on when to use or avoid this tool, nor mentions alternatives.

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