cmw_reset

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It implies a reset to default state but does not mention potential side effects (e.g., losing unsaved settings), whether a connection is assumed, or whether it affects only the specified host/port or all instruments.

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, focused sentence that conveys the essential purpose without superfluous words. It is concise and well-structured for a simple reset operation.

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 simplicity of the tool and the absence of output schema or annotations, the description is minimally complete but lacks important context about when to use it, what happens to the instrument, and how host/port affect the operation. It leaves the agent to infer too much.

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 describes two parameters (host and port) with zero description coverage. The tool description does not explain their purpose, how they relate to the reset operation, or why they are optional. No additional meaning is provided beyond the schema.

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 action (Reset) and target (CMW500) with a specific detail (*RST), making it unambiguous and distinguishing it from similar tools like cmw_preset. The verb-resource pair is specific and the scope is explicit.

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 guidance is provided on when to use this tool versus alternatives such as cmw_preset, cmw_system_all_off, or cmw_clear_limits. It lacks context about prerequisites or situations where a reset is appropriate.

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