adb_remove_forwarding

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

With no annotations, the description carries full responsibility for behavioral disclosure. It states the action (remove) but does not clarify side effects like whether existing connections are disrupted, what happens if the port is not currently forwarded, or if the operation is idempotent. This is a significant gap for a destructive operation.

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?

The description is a single, concise sentence with no filler or redundant information. It is appropriately sized for a tool with one parameter and a simple action.

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 simple utility, the description is minimally viable but incomplete. It lacks usage guidelines and behavioral transparency that would help an AI agent decide when to use it and what to expect. The presence of sibling tools like adb_ensure_forwarding makes the lack of contextual guidance more noticeable.

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 schema provides 100% coverage for the single parameter 'localPort', including a default value, so the description does not need to add parameter details. The baseline of 3 applies because the schema already documents the parameter well.

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 'Remove ADB port forwarding' uses a specific verb and resource, clearly distinguishing it from siblings like adb_forward_port (which adds forwarding) and adb_list_forwardings (which lists them). It leaves no ambiguity about the tool's function.

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 is provided on when to use this tool versus alternatives such as adb_ensure_forwarding or adb_forward_port. There is no mention of prerequisites, typical scenarios, or cases where removal might be unsafe.

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