cmw_scpi_query

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'send query and return response' and does not disclose connection requirements, response format, error behavior, or the fact that queries are typically side-effect-free.

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 one concise sentence with no fluff, which is appropriately sized for the limited information it provides. However, it lacks necessary detail, making it under-specified rather than optimally concise.

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?

With no output schema, no annotations, and low parameter coverage, the description is incomplete. The existence of the very similar sibling cmw_scpi_send is not referenced, and there is no explanation of return format or connection requirements, leaving the tool under-contextualized.

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 only 33% (only 'command' is described). The description text adds no parameter info beyond the schema, merely repeating 'SCPI query'. Host and port semantics remain undocumented, and the description does not compensate for this gap.

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 'Send SCPI query and return response' clearly states the action (send), the resource (SCPI query), and the outcome (return response). It distinguishes from the sibling cmw_scpi_send by explicitly mentioning 'query' and 'return response', which implies a read operation.

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 description provides no explicit guidance on when to use this tool versus alternatives like cmw_scpi_send. It does not mention prerequisites (e.g., connection) or exclude any use cases, leaving the agent without decision support.

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