Pair device

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds real operational context on top: the pairing is a one-time-per-machine operation and the pairing port differs from the connect port. What it does not cover is failure behavior (wrong code, timeout) or what a successful pair returns, which is the remaining gap.

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?

Front-loaded with purpose and the once-per-device constraint, then the on-device steps and the follow-up call. Four sentences all carry usable information, though the UI navigation path could be compressed without loss.

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 two-parameter, no-output-schema tool, the description covers prerequisites, sequencing, port semantics, and the next tool to call. It is close to complete; only error/retry behavior is absent, and no output schema exists that would need explaining.

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 100%, so baseline is 3, but the description goes beyond the schema by explaining that the pairing port is random and distinct from the connect port used later — a semantic point the schema's '(random port, NOT 5555)' only partially conveys. It reinforces rather than merely repeats the field meaning.

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?

States a specific verb and resource ('Pair with an Android 11+ device over Wireless Debugging') and immediately distinguishes itself from the sibling adb_connect by explaining that pairing happens once and adb_connect alone handles reconnection. An agent can route between adb_pair and adb_connect without opening either schema.

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?

Explicit when-to-use ('once per device and computer'), explicit sequencing ('afterwards adb_connect alone reconnects'), and an explicit follow-up instruction ('after pairing succeeds, call adb_connect with the ip:port shown on the main Wireless debugging screen'). Prerequisites (Android 11+, Developer options path) are also given.

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