Pair a device for wireless debugging

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

Annotations already cover the safety profile (readOnly=false, destructive=false, openWorld=true), so the bar is lower. The description still adds real behavioral context the annotations don't carry: pairing codes expire after a couple of minutes, the expected 'Successfully paired' signal, and what to do on failure. It does not contradict the structured hints.

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-loads the core action and the adb command, then layers the flow, port caveat, and expiry warning. Dense but every sentence carries operational value; slightly long, though nothing is wasted.

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 stateful, time-sensitive pairing step with no output schema, the description supplies the prerequisite (code from Settings), the expected success signal, the sequencing into `connect`, and the expiry/failure path. An agent has everything needed to call it correctly and recover from failure.

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 all three parameters are already documented with format, range, and the pairing-vs-connect port distinction. The description reinforces the port distinction and shows the `<host>:<pair_port> <code>` invocation shape, but adds little beyond the schema — baseline 3 is appropriate.

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+resource ('Pair with an Android 11+ device for wireless debugging') and even names the underlying adb command. It clearly distinguishes itself from the sibling `connect` by calling itself 'step one of a two-step flow' and warning that the pairing port is not the connect port.

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?

Explicitly describes when to use it (step one of pairing), what to do next ('after Successfully paired, call connect with the same host'), a concrete exclusion (the pairing port is NOT the connect port), and failure recovery ('ask the user for a fresh code if this fails'). Nothing is left to inference.

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