vna_preset

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

With no annotations provided, the description must carry the full burden of disclosing side effects, but it only says 'Preset VNA' without explaining what that entails (e.g., resetting all instrument settings, interrupting measurements). The SCPI command confirms it's a preset, but the behavioral impact is unexplained.

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 exceptionally brief — a single phrase plus the SCPI command — with no wasted words. For a simple command-like tool, this is appropriately sized, although it lacks structure that could aid comprehension.

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?

The tool is simple, but the description is missing critical context: no parameter explanations, no side-effect disclosure, and no mention of required state (e.g., connection). With no output schema, the description alone is insufficient for an agent to confidently invoke it.

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 input schema shows two parameters (host and port) with zero descriptions, and the description provides no additional meaning for either parameter. With 0% schema coverage, the description completely fails to compensate for the lack of parameter clarity.

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 states the action clearly ('Preset VNA') and even includes the underlying SCPI command 'SYST:PRES' for precision. However, it does not differentiate from the sibling tool 'vna_reset', so there's some ambiguity about the exact scope of the preset operation.

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?

No guidance is given on when to use this tool versus alternatives like 'vna_reset' or 'vna_launch'. There is no mention of prerequisites or typical use cases, leaving the agent to infer when a preset is appropriate.

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