get_usb_interfaces

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

With no annotations provided, the description carries the behavioral disclosure burden. 'List' and 'currently plugged into' signal a read-only, live enumeration, which is helpful. However, it does not describe what happens when no USB adapters are present, whether root is required, or any other runtime behavior beyond the basic listing action.

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, front-loaded sentence with no filler or redundancy. Every word contributes to identifying the tool's action and scope.

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 zero-parameter listing tool with an output schema present, the one-line description is nearly complete. The main shortfall is lack of sibling differentiation, but that is more a usage-guidance gap than a call-completeness gap.

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 tool has zero parameters, so there is no parameter documentation burden on the description. The empty input schema is trivially covered, and the description's focus on the returned resource is sufficient for parameter-related understanding.

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 uses a specific verb ('List') and a specific resource ('USB network adapters currently plugged into the WLAN Pi'), making the tool's function clear. It does not explicitly contrast itself with sibling tools like get_network_interfaces or get_wlan_usb_drivers, but the resource scope is specific enough to avoid major ambiguity.

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?

There is no guidance about when to use this tool versus alternatives such as get_network_interfaces, get_ethernet_interface, or get_wlan_usb_drivers. The phrase 'currently plugged into' implies live hardware enumeration, but no exclusions or use-case conditions are stated.

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