vna_identify

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

No annotations are provided, so the description carries full responsibility. It states the operation is a query and lists the return fields, but it does not disclose whether a connection is required, what happens on error, or any side effects. The read-only nature is only implied by 'Get', not explicitly stated.

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 sentence that front-loads the action and includes essential details (return fields, SCPI command). Every word earns its place; there is no waste or redundancy.

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 query tool, the description covers the basic purpose and return values, but it omits important operational context such as connection requirements, error handling, or any setup steps. Given the lack of annotations and output schema, this leaves the agent with limited guidance for robust invocation.

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 0%, and the description does not mention host or port parameters at all. While these may be self-explanatory, the description adds no meaning beyond the schema, so it fails to compensate for the low coverage.

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 identifies the action ('Get') and the resource ('VNA identification'), and lists the specific return data ('manufacturer, model, serial, firmware'). It also includes the SCPI command (*IDN?), which unambiguously distinguishes it from sibling tools that involve measurement, configuration, or state management.

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?

The usage context is implied: use this tool when you need to identify the instrument. However, there is no explicit guidance on when to use this instead of alternatives like vna_get_status or vna_connect, nor any mention of prerequisites such as an existing connection.

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