vna_configure_sweep

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

No annotations are provided, so the description carries the full burden. While it lists the parameters to configure, it does not disclose that this is a mutating operation, whether an active connection is required, whether existing sweep settings are overwritten, or any side effects on the instrument state.

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 that front-loads the purpose and enumerates the key parameters. Every word earns its place with no redundancy or filler.

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 VNA configuration tool with 8 parameters, no annotations, and no output schema, the description is too thin. It lacks prerequisite information (e.g., connection via host/port), relationship to specialized setter tools, and any indication of what happens when the command is executed.

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 already provides descriptions and defaults for most parameters (75% coverage). The description adds a useful grouping ('frequency range' for start/stop) and names four categories, but it omits averaging_count and does not explain host/port parameters. It adds marginal semantic value beyond the schema.

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 ('Configure sweep parameters') and lists the key parameters (frequency range, points, IF BW, power). It is distinguishable from siblings like vna_set_center_span or vna_set_port_power because it is a bulk configuration tool, but it does not explicitly contrast itself with those alternatives.

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 the specialized setters (e.g., vna_set_center_span, vna_set_averaging, vna_set_port_power). The description does not mention expected context, prerequisites, or exclusions, leaving the agent without decision support for tool selection.

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