serial.connections.list

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

No annotations are provided, so the description carries the full burden. It clearly describes the read-only nature ('List') and the return contents. Since this is a straightforward listing operation, the description adequately discloses behavior without contradictions.

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?

Two concise sentences with no wasted words. The first sentence front-loads the purpose and return fields; the second adds a practical use case. Ideal length for this simple tool.

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 no parameters, no output schema, and no annotations, the description is sufficiently complete. It states what it returns and one key use case. It could hint at prerequisites (e.g., requires an open connection), but it's clear that it lists only open connections.

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 100% schema description coverage. According to guidelines, baseline is 4 for zero parameters. The description appropriately does not add parameter info as none exist.

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 it lists all open serial connections with specific fields (status, port, configuration, timestamps). The verb 'List' and resource scope are precise, and it distinguishes from siblings like 'serial.connection_status' which likely focus on a single connection.

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 tool explicitly mentions a specific use case: 'Useful for recovering connection IDs after context loss.' However, it does not provide explicit when-not-to-use guidance or alternatives, but the given use case is clear and helpful.

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