get_connections

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

No annotations are provided, so the description carries the full burden of disclosing behavior. The word 'List' implies a read-only operation, but the description does not elaborate on side effects, required state, or error conditions. It is accurate but minimal, offering only basic transparency for a simple query tool.

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 sentence of 8 words, with the action verb leading. It is extremely concise and contains no filler, perfectly matching the tool's simple functionality.

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 (zero parameters, no output schema, no annotations), the description provides enough information for an agent to understand the basic purpose. It does not describe the output format, but for a simple list operation this is a minor gap. Overall, it is complete enough for a tool of this complexity.

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% (vacuously). According to the rubric, 0 parameters warrants a baseline of 4. The description adds no parameter details because there are none to describe, so this score reflects the completeness of the schema and the lack of need for further explanation.

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 uses a specific verb ('List') and resource ('open serial connections and their settings'), clearly distinguishing this from sibling tools like list_ports (which likely lists available ports) and open_port (which establishes connections). It unambiguously states what the tool does.

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 by naming the resource (open serial connections), but it does not explicitly state when to use this tool versus alternatives such as list_ports or read_buffer. No exclusions or prerequisites are provided, leaving the agent to infer the appropriate context from the tool name alone.

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