vna_reset

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

With no annotations, the description must carry the full transparency burden. It discloses the action is a reset to default state and adds the *RST SCPI command detail, but it does not mention side effects like clearing calibration, losing settings, or requiring a connection. This is minimal but not misleading.

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, front-loaded sentence that conveys the purpose immediately. Every word earns its place, and there is no redundancy.

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 lacks essential context: no mention of return values (no output schema exists), behavioral consequences, or parameter requirements. For a reset operation, it is unclear whether it affects the current connection or requires one. The minimalism leaves gaps for an agent.

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% and the description does not mention the parameters 'host' or 'port'. While these parameter names are somewhat self-explanatory, the description adds no meaning about their role, optionality, or default values. The tool has 2 params and the description fails to 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 uses a specific verb 'Reset' with a clear resource 'VNA' and state 'default state (*RST)'. It is immediately clear what the tool does and differentiates it from siblings like vna_marker_* or vna_calibration_*, though it may overlap with vna_preset.

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 provides no guidance on when to use this tool versus alternatives such as vna_preset or vna_calibration_start. It does not state prerequisites (e.g., connection) or exclusions. The context signal shows a sibling vna_preset, but no differentiation is made.

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