scpi

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

With no annotations, the description carries the full burden, and it does add real value: the '?' query convention and the fact that binary answers are written to a file rather than inlined. However, it omits that non-query commands can mutate instrument state, and says nothing about permissions, error handling, or whether write commands are safe.

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?

Three short sentences, zero padding, with the core purpose front-loaded before the query and binary-handling details. Every sentence earns its place.

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?

An output schema exists so return values need not be explained. But for an unannotated, arbitrary-command tool that can both read and write instrument state, the description is thin on safety and side-effect disclosure.

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 schema documents neither parameter. The description partially compensates by explaining the '?' query convention for the command parameter and implying binary handling, but it never explains the expect_binary parameter or its relationship to the file-saving behavior.

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?

States a specific verb and resource ('send any SCPI command to the instrument') and labels itself an 'escape hatch', which signals its fallback role relative to the many purpose-specific sibling tools. It's clear what it does, though it stops short of explicitly naming siblings it replaces.

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 'escape hatch' framing implies this is the fallback when no dedicated tool fits, but there is no explicit when-to-use or when-not-to-use statement, and no guidance to prefer the specific siblings (get_idn, get_status, set_channel, etc.). Usage is left to inference.

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