cmw_cell_on

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

The description only states the action of turning on a cell signal. It does not disclose behavioral traits such as effect when already on, required conditions, or side effects. Annotations indicate destructiveHint=false, but description adds minimal additional behavioral context.

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 extremely brief (one phrase), which under-specifies the tool. It does not earn its place as it lacks necessary information, making it incomplete rather than concise.

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 tool's complexity (turning on a cell signal) and the lack of parameter descriptions, the description is vastly incomplete. It does not explain return values, prerequisites, or side effects, despite having an output schema.

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 0%, meaning no property descriptions in the schema. The tool description provides no explanation for the parameters 'alias' or 'params_json', leaving the agent without guidance on what values to provide.

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 action ('turn on LTE cell signal') with verb and resource. However, it does not explicitly differentiate from sibling tools like cmw_cell_off, but the tool name and context imply the opposite action.

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 on when to use this tool versus alternatives. The description does not provide any context about prerequisites, scenarios, or exclusions.

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