dpo2012b_query_scpi

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

Annotations already set readOnlyHint=true and destructiveHint=false, so the description's 'read-only' is redundant. It adds minor context by specifying 'SCPI query' and 'connected DPO2012B', but does not disclose response handling, error behavior, or connection prerequisites beyond the implied 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 a single, direct sentence with no unnecessary words. It is appropriately front-loaded and easy to parse.

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 (one parameter) and the presence of an output schema and annotations, the description provides the core purpose but lacks details about the response format (e.g., string vs. binary) and the requirement that the device be connected. It is adequate but leaves some gaps.

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 schema has one required parameter 'command' with 0% description coverage. The description does not explain what the command should contain (e.g., a valid SCPI command string) or provide examples. It only implies that the parameter is a SCPI command, which is too minimal to compensate for the missing schema description.

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 ('Send'), the resource ('SCPI query'), and the target ('DPO2012B'). It also includes 'read-only', which distinguishes it from sibling tools like dpo2012b_write_scpi and dpo2012b_command, and aligns with the tool's name and annotations.

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 implies usage for read-only SCPI queries, but it does not explicitly mention when to use this tool versus alternatives such as dpo2012b_query_binary or dpo2012b_write_scpi. No exclusions or alternative tool names are provided.

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