vna_measure_vswr

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

No annotations are provided, so the description carries the full burden. It only states the basic action and does not disclose whether the tool is read-only, requires an active connection, or alters the VNA state (e.g., sweeping or setting frequency). This is similar to the 'update_drive' example where insufficient behavioral context was given.

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 fluff or redundancy. Every word adds meaning, and it is front-loaded with the action.

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 simple measurement tool with no output schema and sparse parameter documentation, the description lacks essential context such as return value format, prerequisites, or how it relates to other measurement tools. It is minimally viable but leaves significant gaps for an agent to use it correctly.

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 frequency_hz is documented). The description adds no explanation for host or port parameters, and does not compensate for the low schema coverage. The description does not mention any parameters at all.

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 action: 'Measure VSWR at specific frequency', which is a specific verb+resource combination. It distinguishes itself from sibling tools like vna_measure_return_loss and vna_measure_insertion_loss by focusing on VSWR.

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?

There is no guidance on when to use this tool versus alternatives such as vna_get_s_parameter or vna_measure_return_loss. The description does not mention prerequisites (like being connected) or context (e.g., single-frequency vs sweep).

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