adb_connect

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

With no annotations, the description carries the full behavioral burden and only says the connection is network-based. It omits prerequisites (pairing/tcpip state), failure/timeout behavior, whether an alias must already be registered, and whether the connection persists or applies only to this session.

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?

One short sentence, front-loaded with the verb and resource, with the addressing format attached. No filler to trim.

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 tool with zero annotation coverage, no output schema, and an undocumented parameter, this is too thin. An agent cannot tell what it gets back (device serial? success flag?), what to do if the connection fails, or how the tool relates to the pairing and discovery siblings.

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%, so the description must define 'target' — and it does give the accepted forms 'ip[:port] or alias'. However, it never explains what an alias is, where it comes from, or the expected port default, leaving meaningful ambiguity for the single required parameter.

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?

Specific verb and resource: 'Connect to a device over the network' with the accepted addressing forms (ip[:port] or alias). It clearly differs from adb_list_devices or adb_scan by describing an action rather than a listing, but it never names a sibling to contrast with (e.g., pairing via adb_pair_qr_finish), so it stops short of a 5.

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 choose this over adb_scan, adb_pair_qr_start/finish, or adb_list_devices, and no preconditions such as prior pairing or wireless-debugging being enabled. The agent must infer the workflow entirely.

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