cmw_set_meas_port

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

The description only states the action but not side effects or behavioral traits. With only destructiveHint=false provided, the description does not add beyond the annotation. For a write-like operation, it should mention if it requires connection or affects state.

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 extremely short (one phrase). While it is front-loaded, it sacrifices necessary detail. Every sentence should earn its place, but here the brevity undermines usefulness.

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 description is completely inadequate for a tool with 2 optional parameters, an output schema, and many siblings. It does not explain the purpose of parameters, when to set measurement port, or what the output represents.

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%, yet the description does not explain the parameters 'alias' and 'params_json'. Without any parameter information, the agent cannot understand how to invoke the tool correctly.

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 it sets measurement signal path/port, which is a clear verb+resource. However, it does not differentiate from the sibling tool 'cmw_set_sign_port', which likely has a similar purpose. The title is null, reducing clarity.

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 on when to use this tool versus alternatives like cmw_set_sign_port. There is no mention of context, prerequisites, or when not to use it.

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