sdg1062x_query_scpi

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description aligns by stating 'non-destructive query'. It adds minimal extra context, such as that commands are documented by the Siglent guide, but doesn't describe response behavior or error handling. No contradiction with annotations.

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 sentence of 11 words, immediately front-loading the core action and scope. Every word contributes value, and it is appropriately sized for a simple tool with one parameter.

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 low complexity (one parameter), strong annotations, and presence of an output schema, the description covers the essential purpose and safety profile. It could mention that return values are provided via the output schema, but the current wording is sufficient for an agent to select and invoke the tool correctly.

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?

With schema description coverage at 0%, the description must clarify the 'command' parameter. It indicates the command should be a query documented by the Siglent programming guide, which adds valuable context but doesn't explain the expected format (e.g., trailing '?') or provide examples. This is partial compensation.

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 uses a specific verb ('send') and identifies the resource ('a non-destructive query documented by the Siglent programming guide'). It clearly conveys a read operation on the instrument but doesn't explicitly mention the return value or differentiate from sibling query tools beyond the 'non-destructive' qualifier.

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 use for reading/querying the instrument via SCPI commands and contrasts with write operations through the word 'query' and 'non-destructive'. However, it provides no explicit when-to-use vs alternatives, such as naming the sibling write_scpi tool or other query methods.

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