scpi_query

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

Annotations indicate readOnlyHint=true, which sets the safety baseline. The description adds a valuable behavioral detail by noting CHDR is OFF, so responses contain only values without headers. However, it does not mention potential errors from malformed arbitrary commands or timeout behavior, which is a moderate 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 three sentences, each serving a distinct purpose: purpose, usage, and an important response-format caveat. It is front-loaded and free of redundant information.

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 tool's simplicity, the description covers the essential aspects: what it does, when to use it, and a key response-format nuance. With readOnlyHint and full schema coverage, it is fairly complete for an escape-hatch tool, though it could mention error behavior.

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 100%, with both command and timeout_ms documented with examples. The description does not add further parameter-specific details beyond what the schema provides, so a baseline score is appropriate.

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 'Send an arbitrary SCPI query to the waveform generator and return the response,' specifying the verb, resource, and action. It distinguishes itself from siblings by positioning itself as an escape hatch for commands not covered by other tools.

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 explicitly advises using this as an escape hatch for commands not covered by other tools, providing clear when-to-use context. It does not explicitly name alternatives like scpi_command for write commands, so it's not fully exhaustive but still offers solid guidance.

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