vna_scpi_send

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the '(no response)' return behavior, which is useful, but omits other behavioral context such as connection requirements, potential side effects of sending raw commands, or error handling. This is a minimal level of transparency.

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, concise sentence with no filler. It front-loads the core action and includes the essential response behavior. Every word contributes to comprehension, making it highly efficient.

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?

For a raw command tool with no annotations, output schema, or additional context, the description is under-specified. It lacks usage guidance, parameter elaboration, and safety/connection caveats that would be expected for a raw SCPI sender, leaving the agent without sufficient context to invoke it confidently in diverse scenarios.

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 only 33% (only 'command' has a description), and the description does not add any parameter-level details. The roles of 'host' and 'port' are left unexplained, and the format of 'command' is not elaborated, leaving notable ambiguity for an agent.

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 tool's function with a specific verb and resource: 'Send raw SCPI command' and explicitly notes '(no response)', which distinguishes it from sibling vna_scpi_query. This makes the purpose unambiguous and differentiates it from similar 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 '(no response)' qualifier implies when to use it (when a response is not needed) and indirectly points to vna_scpi_query for queries, but it does not explicitly name alternatives or provide exclusion criteria. The usage context is implied rather than directly stated.

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