device_connection

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

With no annotations, the description carries the full burden, and it does disclose one genuine side effect: selection clears UI indices, plus the multi-device defaulting rule. It leaves out failure behavior (what connect returns on an unreachable host), whether pairing consumes the code, and permission/authorization needs, so the disclosure is partial rather than rich.

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 tight sentences with the operation list front-loaded and the caveats second; no filler. The telegraphic style ('List/select...') costs a little readability but every clause carries information.

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?

An output schema exists so return values need no explanation, but for a stateful connection tool with four undocumented parameters and zero annotations, the description is too thin. It omits required-field expectations (nothing is required, so which params select which action), prerequisites for pairing, and post-connect state.

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 description coverage is 0% and all four parameters are undocumented in the schema, so the description must compensate. It only maps partially: 'host:port' hints at the address format and 'pair' implies the pairing code, but serial (the key selector for multi-device selection) and the enumerated action values are never explained.

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 names concrete verbs (list/select/connect/disconnect/pair) against a concrete resource (ADB devices, host:port), so the agent knows this is the device-connection lifecycle tool rather than a control/status tool. It is clear enough to separate from siblings like device_control or get_device_status, though it never names those alternatives explicitly.

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?

It conveys a situational hint ('no arbitrary default when multiple devices are attached') but gives no when-to-use vs when-not guidance and does not name any sibling or alternative path. Nothing says when to use pair versus connect, or what prerequisite state a device must be in for each.

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