usbtmc_list_connected_devices

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds value by detailing the return structure and providing an example, which clarifies expected output behavior. No contradictory or missing behavioral traits are evident.

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, leading with the main action, followed by a clear Returns section and a concrete example. Every sentence contributes useful information without being overly verbose, making it efficient for an agent to parse.

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's simplicity (no parameters, read-only, output schema present), the description is complete. It fully specifies the returned fields (count, devices with device_id, manufacturer, product, serial_number) and includes an illustrative example, leaving no major gaps.

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?

This tool has zero parameters, so the baseline is 4. The description correctly avoids parameter details, and the input schema (empty properties) confirms no parameters need explanation.

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 'List all currently connected (active) USBTMC devices', which is a specific verb+resource. However, it does not explicitly distinguish this from the sibling tool 'usbtmc_list_devices', though the 'connected' qualifier provides some differentiation.

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 usage for retrieving currently connected USBTMC devices, but provides no explicit when-to-use guidance or alternatives. It does not mention when to prefer this over 'usbtmc_list_devices' or other siblings, leaving the agent to infer the use case.

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