cmw_scpi_send

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

With no annotations provided, the description carries full burden for behavioral disclosure. It does disclose the key trait that there is no response, which is important. However, it omits other behavioral context such as whether a prior connection via cmw_connect is required, how errors are handled, or whether commands are queued synchronously.

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 with no wasted words. It is front-loaded with the action and resource. However, it is almost too terse, and a bit more structural detail could improve it without sacrificing conciseness.

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 incomplete for a tool with 3 parameters and no annotations or output schema. It does not mention prerequisites (e.g., connected device), whether host/port are optional with defaults, or what side effects occur. An agent would need to infer too much from the name alone.

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 coverage is only 33% (only 'command' has a description). The description does not add meaningful details about 'host' or 'port' parameters, such as defaults, optionality, or format. It merely implies that the command goes to the CMW500, leaving the agent to guess how host/port are used.

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 a specific action ('Send raw SCPI command') and a specific resource ('CMW500'). The parenthetical '(no response)' explicitly distinguishes it from its sibling tool cmw_scpi_query, which presumably returns a response.

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 phrase '(no response)' provides clear context that this tool is for fire-and-forget commands where no reply is expected. It implies a contrast with cmw_scpi_query, but does not explicitly name an alternative or state when to use one over the other.

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