cmw_lte_cell_off

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

With no annotations present, the description must disclose behavioral impact, but it only states the action without mentioning side effects, reversibility, required state, or consequences for ongoing measurements. An agent cannot infer whether this is safe or catastrophic.

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?

At only four words, it is too sparse rather than concise. It lacks essential context that could be added without significant length, so the brevity is under-specification, not effective compression.

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?

The tool description is a fragment. It does not explain return values, errors, or preconditions, and the lack of any structured metadata (no annotations, no output schema) leaves the agent with insufficient information to safely invoke the tool.

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 two parameters (host, port) have no descriptions in the schema and the tool description does not explain their meaning or format. Schema coverage is 0%, and the description fails to compensate, leaving parameter semantics entirely undocumented.

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 specifies a single action ('Turn off') applied to a specific resource ('LTE cell'), which distinguishes it from the sibling 'cmw_lte_cell_on'. Despite brevity, the verb+resource format is unambiguous within the CMW context.

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 information is provided about when to use this tool versus alternatives like cmw_lte_cell_on or cmw_system_all_off. The description offers no usage scenarios, prerequisites, or exclusions.

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