usbtmc_connect

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description discloses important behaviors: the need for a unique match, failure when multiple devices match, and a limit of 16 simultaneous connections. This adds meaningful context that annotations do not cover.

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 well-structured with a clear opening statement, then Args, Returns, and Note sections. It is slightly longer than necessary but every section adds valuable information without redundant fluff.

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 description covers success and error return formats, the purpose of device_id, uniqueness requirements, and connection limits. Given the tool's complexity (nested parameters, failure modes, connection lifecycle), this is a complete and self-sufficient description.

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%, so the description compensates by listing all three parameters (manufacturer, product, serial_number) and their roles, including noting serial_number as 'most specific.' While schema descriptions already contain similar details, the description provides the functional context needed to choose criteria.

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 states the tool's function with a specific verb and resource: 'Connect to a USBTMC device and receive a device_id for subsequent operations.' It distinguishes itself from sibling tools by focusing on establishing a connection, not listing, sending, or disconnecting.

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 description implies when to use the tool (before subsequent operations) and provides guidance on how to avoid failure: 'If multiple devices match the criteria, the connection will fail - provide more specific criteria.' It does not explicitly mention alternatives, but the context is clear enough without them.

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