cmw_cell_state_all

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

The annotation already declares readOnlyHint=true, so the description's addition of 'complete status including adjustment status' provides some extra behavioral scope but no details on side effects, prerequisites, or data freshness beyond what annotations indicate.

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. However, it is in Chinese, which may hinder a non-Chinese-speaking agent, but the structure is efficient with no wasted words.

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 presence of a similar sibling 'cmw_cell_state' and two unexplained parameters, the description lacks critical context. The output schema is present, but the description does not clarify when to use this over other cell state tools.

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%, and the tool description does not explain the two parameters 'alias' and 'params_json'. No meaning is added beyond the schema, which is insufficient for proper agent usage.

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 queries the complete status of a cell including adjustment state. The name 'cmw_cell_state_all' distinguishes it from sibling 'cmw_cell_state' by implying a more comprehensive query.

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 querying full cell status but provides no explicit guidance on when to use this tool versus alternatives like 'cmw_cell_state' or prerequisites.

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