list_serial_ports

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

Without annotations, the description details the returned fields (device, description, VID, PID, etc.) and adds conditional behavior about monitoring status. It does not mention side effects or permissions, but listing ports is inherently safe.

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 neatly organized into sections ('When to call', 'What it returns', 'Loop step') with no unnecessary words. Every sentence serves a purpose.

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?

Despite having no output schema, the description fully explains the return value and monitoring behavior. It also gives context on when and how to use the tool, making it self-contained.

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 schema coverage is 100%. The baseline score is 4, and the description correctly provides no redundant parameter information.

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 the tool lists serial ports and provides specific use cases (checking which port corresponds to which board, inspecting monitoring targets). It distinguishes itself from sibling log tools.

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 gives explicit guidance on when to call (port/board identification, monitoring check) and notes it is a one-time pre-check. It lacks explicit 'when not to use' or alternatives, but the context is clear.

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