usb_devices

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

Description claims a read-only operation ('List', 'Reads'), but annotations set destructiveHint=true, which contradicts. This is a serious inconsistency. The description does add value by stating it's local, but the contradiction overrides.

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 sentences with no waste, front-loaded with action and returns. Efficient and clear.

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?

List of return fields is provided, though no output schema exists. Tool is simple and description covers essentials. Minor gap: does not mention if any filtering is possible (but parameters are none).

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?

No parameters exist (schema coverage 100%). Baseline score of 4 is appropriate since description adds no param info but none is needed.

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?

Description clearly states it lists USB devices, specifies return fields (name, vendor, product ID, speed, manufacturer), and distinguishes itself from sibling tools by focusing on USB enumeration.

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?

Description implies local-only usage and explicitly mentions no remote enumeration, but does not provide alternatives or when-not-to-use scenarios. Good context but no exclusions.

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