adb_connect

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

No annotations are provided, so the description carries the burden. It states the action (connecting to a device) but doesn't disclose what happens on failure (e.g., if the device isn't paired), whether connection state persists, or what the response/return looks like. The 'wireless-debug' qualifier adds some context about prerequisites but not enough for full transparency on a connection-establishing 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?

Single efficient sentence, no filler. The parenthetical adds the key clarification about which port type this is. Every word earns its place.

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?

For a connection-establishing tool with no annotations, no output schema, and 0% schema description coverage, the description is thin. It doesn't explain failure modes, whether pairing is a prerequisite (beyond implying 'wireless-debug'), what happens on successful connect, or how this differs from adb_pair. Given the sibling set of 24 ADB tools, more context about connection lifecycle would be valuable.

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% and there are 2 params with no descriptions. The description mentions 'host:port' as a unit, which maps to the two parameters, and calls out it's the wireless-debug port. However, it doesn't clarify host format (IP vs hostname), port range constraints, or whether the port differs from the pairing port shown in the wireless-debug UI. With no schema descriptions, the description should compensate more.

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 ('Connect') with a clear resource (device ADB endpoint host:port), and clarifies this is the wireless-debug 'connect' port. It's clear what the tool does, though it doesn't explicitly distinguish from its sibling adb_pair or adb_disconnect beyond the action itself.

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?

No guidance on when to use this tool vs alternatives. Siblings like adb_pair, adb_disconnect, and adb_devices exist but there's no mention of when connect is appropriate versus these. The description mentions wireless-debug 'connect' port, which implies pairing context, but no explicit when/when-not guidance is provided.

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