serial_list_connections

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description confirms this by stating it 'lists' connections and does not modify anything. It adds that the tool returns a formatted list or error message, and provides example output, which is helpful.

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 well-structured with a summary line, followed by details on arguments and returns. It is concise but includes a detailed JSON example which aids understanding. Minor redundancy with the Args/Returns section.

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 low parameter count (1), high annotation coverage, and presence of an output schema, the description is fairly complete. It explains the return format and provides example output. Could mention that this only shows active connections (not all ports), which is implied but not explicit.

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?

Schema coverage is 0% (the single parameter 'params' is a wrapper, not directly described). The description explains the response_format parameter and its default, which adds value beyond the schema. However, the description could better clarify that 'params' is a wrapper object.

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 all active serial port connections, distinguishing it from sibling tools like serial_open, serial_close, and serial_read which perform different operations. The verb 'list' and resource 'active serial port connections' are specific.

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 provides clear context for use (listing active connections) and implies no modification. However, it does not explicitly state when not to use it or differentiate from similar tools like serial_list_ports (which lists available ports, not connections).

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