afg2125_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 simply repeats 'read-only' without adding new behavioral context. It does not disclose response format, timeout behavior, or whether the command should include a '?' suffix. The only added context is 'connected AFG-2125', which is not behavioral.

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, clear sentence with no wasted words. It efficiently conveys the core purpose.

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 an output schema present and only one parameter, the description is mostly adequate. It specifies the target instrument and read-only nature. However, it lacks details on valid SCPI query formats or whether the tool automatically appends '?', but given the output schema and simple context, the completeness is acceptable.

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 0%, so the description must compensate for the single 'command' parameter. It only says 'Send a read-only SCPI query' which implies the command is a SCPI query string, but it does not provide examples, mandatory '?' syntax, or error handling. This is minimal and does not fully compensate for the lack of schema descriptions.

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), resource (read-only SCPI query), and scope (connected AFG-2125). It distinguishes from write operations and other instrument-specific query tools by naming the instrument and specifying read-only.

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 reading instrument state via SCPI queries. It does not explicitly name alternatives like afg2125_write_scpi, but the 'read-only' qualifier provides clear context that this is not for writing. No exclusions are stated, but the read-only nature is a strong implicit guideline.

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