adb_forward

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'forward' but does not explain side effects (e.g., port binding, potential conflicts), required permissions, or behavior on failure. This is insufficient for a complete understanding.

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 sentence that front-loads the action and key parameters. It is concise and to the point, though it could benefit from additional detail without becoming verbose.

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 complexity (3 parameters, output schema exists but unknown), the description is too brief. It does not explain the output format, success/error indications, or how the tool behaves in various scenarios (e.g., port already in use). The output schema might provide some of this, but without seeing it, the description alone is incomplete.

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 coverage is 0%, so the description must add meaning. It explains that local_port and remote_port are tcp ports, but does not describe the serial parameter or provide formatting constraints, valid ranges, or examples. The description adds minimal value beyond the schema's type information.

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 tool's purpose: forward host port to device port using adb forward. It specifies the verb 'Forward', the resource 'host tcp:LOCAL_PORT to device tcp:REMOTE_PORT', and the mechanism 'adb forward'. This distinguishes it from siblings like adb_reverse.

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 on when to use this tool versus alternatives like adb_reverse or adb_shell. The description does not mention prerequisites, error conditions, or when not to use it. A score of 2 reflects the lack of usage context.

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