Reverse a device port to the host

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description only needs to add context beyond them. It does add the forwarding direction semantics, but says nothing about lifecycle: whether the reverse persists beyond the session, or that the default behavior replaces an existing reverse when the spec differs (the no_rebind parameter implies rebinding, which is left to the schema).

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 sentences, zero waste, with the directionality semantics front-loaded before the use case. Nothing repeats the title or schema verbatim.

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 4-param mutation tool with full schema coverage, annotations, and no output schema, this covers what an agent needs to call it correctly. The only omissions are peripheral: the rebind/replace default and the existence of remove_reverse as the teardown counterpart.

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. The description still earns above baseline by explaining that 'remote' is the device-side listening spec and 'local' is the host-side target, which resolves the naming ambiguity that the terse schema descriptions ('Device-side listen spec') only partly cover.

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?

Names a specific verb+resource ('Create a reverse socket connection (`adb reverse`)') and disambiguates the exact point that confuses agents versus forward_port: which side listens and which side connects. An agent can distinguish it from 'forward_port' 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?

Gives a concrete when-to-use ('let device-side code ... reach a server running on your machine'), which is the canonical scenario. It stops short of naming the sibling alternative forward_port for the opposite direction or pointing at remove_reverse for teardown, so it doesn't reach explicit when-not/alternatives.

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