vna_output_on

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

There are no annotations to fall back on, so the description carries full responsibility. It discloses no side effects, safety concerns, or behavior when the output is already enabled. This is a critical gap for a hardware-affecting operation.

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, but it is overly terse and lacks any additional structure or context. While it is not verbose, the brevity comes at the expense of necessary information, making it merely adequate.

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 tool affects RF output and has two connection parameters, the description should at least mention that a connection is required or describe the effect on the instrument. With no output schema and no extra context, an agent cannot reasonably infer safe and correct usage.

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 has two parameters (host and port) with zero description coverage. The description does not mention these parameters or their purpose, leaving the agent without any semantic understanding of what values to provide.

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 'Enable RF output' clearly states a specific action with a resource, and the verb 'enable' distinguishes it from its sibling vna_output_off. However, it does not elaborate on what 'RF output' encompasses in the VNA context, so it stops short of a 5.

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. It does not mention prerequisites like needing an active connection or that it should be used before measurements, nor does it reference the sibling vna_output_off.

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