adb_tunnel_close

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

No annotations exist, so the description carries the burden. It discloses side effects: removal of adb forward/reverse entry and dropping from cleanup registry. This adds behavioral context beyond a simple 'Close'.

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 with no extraneous words. The main action is first, followed by behavioral details and a cross-reference to a sibling tool. Ideal structure for quick comprehension.

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?

Complete for a simple close tool with one parameter. The description explains what happens after closing (entry removal, registry drop) and how to get tunnel IDs. No output schema needed.

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?

The single parameter 'id' is fully described with format (tun_XXXXXX) and special value 'all'. Schema coverage is 100%, but the description adds meaningful explanation beyond the schema's type and optional description.

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 clearly states the action ('Close'), resource ('managed tunnel'), and two modes ('by ID' or 'all at once'). It distinguishes from sibling tools like adb_tunnel_open and adb_tunnel_list.

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?

Provides guidance on using adb_tunnel_list to find tunnel IDs before closing. Could be more explicit about when not to use (e.g., if the tunnel is not managed), but the reference to 'managed tunnel' implies this limitation.

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