serial_list

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

No annotations are provided, so the description carries the burden — and it discloses non-obvious behavior: the tool not only enumerates ports but also probes chip identity and emits driver recommendations. It is implicitly a non-destructive read, though that is never stated outright.

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?

Three compact sentences, front-loaded with what it lists, then the value-add, then the call trigger. No filler.

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?

Zero parameters, an output schema that covers return values, and a simple read operation — the description supplies exactly what an agent needs to select and invoke it correctly, with the extra chip/driver detail as a bonus.

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 takes zero parameters, so there is nothing to misinterpret; baseline 4 applies. Schema coverage is 100% and no parameter semantics are 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?

States a specific verb+resource (列出系统可用串口) and then extends it with concrete added capability — recognizing CH340/CP2102/FT232 USB-serial chips and suggesting drivers. This cleanly distinguishes it from sibling read/write tools like serial_open, serial_read, and driver_list.

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 an explicit trigger scenario: 'when the board is not visible in the serial port list, call this first.' That is a real when-to-use cue, but no alternatives or exclusions are named (e.g., when to prefer driver_list or probe_list instead).

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