cmw_connect

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It simply states 'Connect' without elaborating on side effects (e.g., whether an existing connection is replaced), error handling, or persistence of the connection. For a state-changing network operation, this is a transparency gap.

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, front-loaded sentence with no filler words. It conveys the essential information in a compact form, appropriate for a simple connect 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?

The tool is simple with two parameters and no output schema, so the description is minimally adequate. However, it omits important contextual details such as the need to call this before other cmw_* commands, default connection behavior from config, and whether the connection is persistent or requires a subsequent disconnect. These gaps could leave an agent uncertain about operational flow.

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 already documents both host and port with descriptions, achieving 100% schema coverage. The description's phrase 'specified host:port' adds no new meaning beyond what the schema provides, so it meets the baseline without adding value.

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 (Connect), the target (CMW500), and the addressing mechanism (host:port). This distinguishes it from sibling tools like cmw_disconnect and cmw_discover, which serve different purposes.

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 tool name and description imply it should be used to establish a connection before other cmw_* operations, but no explicit guidance is given about prerequisites, alternatives, or when not to use it. The context of sibling tools suggests usage, but the description itself does not provide explicit when/when-not guidance.

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