Open a VISA instrument

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

With no annotations, the description carries the full behavioral burden. It usefully discloses a non-obvious normalization behavior (bare IP vs host:port mapping to INSTR vs SOCKET), but says nothing about session lifecycle, idempotency of re-opening, or permissions, leaving real gaps for a 6-param connection tool.

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?

Two tightly written sentences with the core action and the resource-format rule front-loaded; nothing is wasted or repetitive.

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?

The output schema means return values need not be described, and the resource-format guidance covers the required parameter. However, for a tool exposing serial/termination/timeout parameters, the absence of any explanation for those knobs and the lack of lifecycle pointers (e.g., pairing with close_instrument) leaves it only partially complete.

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 17% (only 'resource' is documented in the schema). The description adds valuable format semantics for that one parameter, but baud_rate, timeout_ms, read_termination, and write_termination are unexplained in both schema and description, and 'identify' is only implied by 'optionally query *IDN?'.

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?

States a specific verb and resource ('Open an instrument') and adds the optional identify behavior. It is clearly distinguishable from siblings like close_instrument and list_instruments, though it never names them explicitly.

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?

Gives concrete guidance on which resource format the agent should pass ('Bare IPs become TCPIP::<ip>::INSTR. host:port becomes a raw TCP SOCKET') and even names typical ports and a specific device, which is genuinely useful usage context. It lacks explicit when-not-to-use or alternative-tool routing.

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