cmw_lte_cell_on

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

No annotations are provided, so the description must fully disclose behavior. It only states the action without mentioning side effects, prerequisites, reversibility, or what state changes occur. There is no information about whether the operation is safe, requires prior setup, or has any impact on other tools.

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 with a helpful parenthetical clarification. It is front-loaded with the core action and contains no unnecessary words or structure.

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?

With no output schema and no annotations, the description is insufficient for a mutation tool. It fails to explain parameters, return behavior, preconditions, or consequences, leaving critical gaps for reliable invocation.

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 input schema has two parameters (host, port) with zero description coverage, and the description does not mention them at all. The agent receives no guidance on what values to provide or their purpose, making parameter handling entirely opaque.

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 'Turn on LTE cell' and clarifies with '(start base station emulation)', making the specific action and resource unambiguous. It naturally distinguishes itself from siblings like cmw_lte_cell_off and cmw_lte_configure_cell.

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 by indicating it starts base station emulation, but it provides no explicit guidance on when to use it versus alternatives or what preconditions exist (e.g., needing configuration first). It lacks any when-not-to-use or alternative references.

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