cmw_preset

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

The description adds minimal value beyond the tool name and the 'destructiveHint' annotation. It does not detail side effects, such as losing current settings, nor does it describe what 'preset state' entails.

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 overly terse (one short sentence). While it is front-loaded, it sacrifices essential information for brevity.

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 complexity of two undocumented parameters and the presence of an output schema (not described), the description is insufficient. It lacks return value info and parameter guidance.

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 zero description coverage, and the tool description does not explain the two parameters ('alias' and 'params_json'). The agent has no information on how to use them.

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 states a specific verb ('恢复' meaning restore) and resource ('CMW500 to preset state'), making the tool's function clear. However, it does not differentiate from the sibling tool 'cmw_recall_state', which could cause confusion.

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 provides no guidance on when to use this tool versus its siblings or any prerequisites. Agents receive no context for appropriate usage.

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