adb_forward_port

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'Set up' and the default mapping, but does not mention side effects (e.g., whether existing forwards are overwritten), prerequisites (e.g., a connected device), or whether the operation is idempotent. This is a significant transparency gap for a mutating tool.

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, front-loaded sentence with no filler. It efficiently conveys the tool's purpose and default configuration, making it ideal for quick scanning.

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?

Given the tool's simplicity (2 params, full schema coverage, no output schema), the description covers the core purpose and defaults. However, the absence of annotations means the description should also disclose behavioral traits like idempotency or prerequisites, which it does not. It is minimally viable but leaves gaps.

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 input schema already covers both parameters with descriptions at 100% coverage. The description adds value by showing the relationship between localPort and remoteAbstract through the default mapping, which clarifies that localPort is the TCP port and remoteAbstract is the abstract socket in the forwarding rule.

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 uses a specific verb ('Set up') and resource ('ADB port forwarding'), and it provides the default mapping, which clearly distinguishes this from sibling tools like adb_list_forwardings and adb_remove_forwarding. The default tcp:9222 -> localabstract:chrome_devtools_remote makes the intent unambiguous.

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?

The description clearly indicates the common use case via the default mapping, implying when to use it (e.g., for Chrome DevTools remote debugging). However, it does not explicitly mention exclusions or alternatives like adb_ensure_forwarding, so it lacks explicit when-not guidance.

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