connect_serial

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

With no annotations, the description must disclose behavioral effects, but it only says 'Connect' and gives use cases. It does not explain whether the connection persists, how to end it, whether it requires physical access, or what success/error output looks like. This is a significant gap for a stateful connect operation.

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 two short sentences, front-loaded with the core action and resource, and contains no redundant phrasing. Every word adds value.

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?

The description is incomplete for a stateful tool with no annotations and no output schema. It lacks critical context about the connection lifecycle, how to interact with the session afterward, and any side effects. The schema covers parameters but not the behavioral context needed for correct invocation.

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 input schema covers 100% of parameters with detailed descriptions, so the description does not need to add parameter semantics. The baseline of 3 applies because the schema does the heavy lifting and the description adds no extra parameter context beyond naming the serial 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 clearly states the action and resource: 'Connect to an OpenWrt router via serial port (UART/COM)'. It also differentiates from siblings by specifying the serial transport and use cases (boot logs, recovery, low-level debugging), making its purpose distinct from network-based connect_router.

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 when to use it ('useful for boot logs, recovery, and low-level debugging'), but it does not explicitly mention alternatives or when not to use it. This is slightly below the explicit alternatives standard.

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