list_ports

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

With no annotations available, the description carries the full burden of behavioral disclosure. It does not state output format, filtering, permissions, or side effects. The note about preferring /dev/cu.* over /dev/tty.* on macOS is a useful platform-specific behavior, but alone it does not provide significant transparency.

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 text is reasonably brief and front-loaded with the main action, but it includes malformed trailing text that appears to be an accidental copy of sibling names. Every sentence should earn its place; the trailing corruption and low-value generic sentence reduce the score.

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 no-argument list tool, the description covers the core action and adds useful field-level identification clues plus a macOS selection hint. However, output schema exists but is not shown, so return-value format is not described in the text; overall it is minimally viable for selecting and invoking this tool.

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 parameter semantics are fully satisfied. The description even adds value by explaining how to interpret the fields that will be returned (description, manufacturer, vid/pid) to identify the correct port.

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 appears to be present; however, the text is truncated and garbled at the end ('...is_clear_buffer' from a sibling list spills into the description). It does not provide a clear statement of the tool's purpose. A one-sentence generic description like 'List serial ports' is further undercut by the corrupted trailing text.

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?

No guidance is given on when to use this tool versus alternatives. The only usable context is embedded in field-specific hints for identifying boards, which is post-selection guidance, not invocation reasoning.

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