vna_set_center_span

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Configure frequency via center and span' and does not mention any side effects, required state (e.g., connection), error conditions, or whether this is a write operation beyond the verb 'configure'.

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 is front-loaded with the key action. There is no wasted wording, and every word earns its place.

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 the lack of annotations and output schema, the description is too thin for an agent to invoke the tool confidently. It omits information about how host and port are used, what the expected behavior is when parameters are out of range, and what the tool returns. For a simple setter, it is still incomplete because host and port are undocumented.

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 schema already describes center_freq_hz and span_hz with basic descriptions. The tool description adds no extra meaning for these parameters and completely ignores the host and port parameters, which have no schema descriptions. At 50% schema description coverage, the description does not compensate for the missing parameter information.

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 frequency via center and span' clearly states the action (configure frequency) and the method (center and span). It is specific enough to indicate the tool's role, though it does not explicitly distinguish it from sibling tools like vna_configure_sweep.

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 on when to use this tool versus alternatives such as vna_configure_sweep. There is no mention of prerequisites, exclusions, or scenarios where another tool is more appropriate.

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