list_serial_ports

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

No annotations are provided, so the description must carry the behavioral disclosure burden. The verb 'List' clearly signals a read-only operation, which is the central behavioral trait. However, it does not mention any potential side effects, permissions, or return format details, leaving some ambiguity about whether it blocks or requires setup.

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 words. It communicates the exact purpose efficiently, making every word count.

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 (0 parameters, no output schema) and the sibling context, the description is complete. It tells the agent exactly what to expect—a list of serial ports—and no further caveats or details are necessary for correct invocation.

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 and schema description coverage is 100% (trivially). Per the rubric, a baseline of 4 is appropriate since there is nothing to document. The description adds no parameter details, but none 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?

The description 'List available serial ports on the system' uses a specific verb ('List'), names the resource ('serial ports'), and defines scope ('on the system'). It clearly distinguishes from sibling tools like serial_write, serial_log, and connect_serial, which involve actions beyond listing.

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: call this when you need to enumerate available serial ports. However, it offers no explicit guidance on when to use it versus alternatives, such as when checking connection status or before connecting to a serial port. There are no exclusion cues or sibling references.

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