vna_set_averaging

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

Because there are no annotations, the description carries the full burden of behavioral disclosure. It merely states 'Configure sweep averaging' without explaining side effects, whether it overwrites existing averaging settings, if it requires an active connection, or any other behavioral traits. This is insufficient for a configuration action.

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 extremely concise—one short phrase—which makes it easy to parse. However, it is borderline under-specified; it reads more like a label than a full description. It is not as tautological as 'Process', but it lacks the supportive detail expected for a functional description.

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?

Given there are no annotations, no output schema, and incomplete parameter coverage, the description needs to provide more context. It does not mention connection requirements, default behavior, or how averaging affects measurements. The single sentence is too sparse to be considered complete for a configuration tool.

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 'count' has a description). The tool description adds no additional meaning for 'host' or 'port', which remain entirely undocumented. While 'count' is described in the schema as 'Number of averages (1 = off)', the description itself does not explain how it relates to the sweep averaging behavior.

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 'Configure sweep averaging' uses a specific verb ('configure') and identifies the resource ('sweep averaging'), clearly indicating the tool's function. However, it does not distinguish it from the sibling 'vna_configure_sweep', which might also be seen as configuring sweep-related settings, so it loses a point for lack of differentiation.

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 provided about when to use this tool versus alternatives like 'vna_configure_sweep' or other sweep settings. There is no mention of prerequisites (e.g., needing a connected instrument) or context such as setting averaging before a measurement.

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