cmw_preset

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

Annotations are absent, so the description carries full responsibility for disclosing behavior. It fails to mention side effects (e.g., resetting all settings), prerequisites (e.g., connection), or the impact on the current system state. The text is a mere label with no behavioral detail.

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 short sentence, but this is under-specification rather than conciseness. It uses few words but conveys no meaningful information, so the sentence does not earn its place.

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 absence of annotations and output schema, the description is severely incomplete. Even with only two simple parameters, the tool's core function is undefined, making it impossible for an agent to use it correctly.

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 schema lists only 'host' and 'port' with no descriptions, and the description makes no reference to these parameters. With 0% schema description coverage, the description does nothing to compensate, leaving their purpose and requirements completely unknown.

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 'Full system preset of CMW500' is a noun phrase with no verb or action, essentially restating the tool name 'cmw_preset'. It does not state whether the tool applies a preset, returns one, or resets the system, and it fails to distinguish itself from sibling tools like cmw_load_state or cmw_apply_template.

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?

There is no guidance on when to use this tool versus alternatives such as cmw_load_state, cmw_apply_template, or cmw_reset. The description provides no context for tool selection, leaving the agent without decision criteria.

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