adb_forward_remove

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

No annotations are provided, so the description must convey behavioral traits. It states the tool removes forwards, which is a destructive action, but does not disclose potential failure modes or permission requirements. The description is adequate for a simple removal 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 consists of two short, clear sentences that immediately convey the tool's purpose and recommended usage. Every word is necessary; no verbosity or repetition.

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 has 2 optional parameters, no output schema, and no annotations, the description covers the essential aspects: what it does, when to use it, and the key parameter behavior. It does not elaborate on error cases or success indicators, but for a cleanup tool this is sufficient.

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 provides descriptions for both parameters (local and device) with 100% coverage. The description adds extra meaning by explaining that omitting 'local' removes all forwards and mentions an 'AF2 fix: format-validated', which adds value beyond the schema.

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 (remove) and the resource (port forward), specifying the direction (host → device) and the option to remove all forwards. This distinguishes it from sibling tools like adb_forward (add) and adb_forward_list (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?

The description provides context on when to use the tool ('Use after testing to clean up'), but does not explicitly mention when not to use it or compare with alternatives like adb_reverse_remove. Nonetheless, the guidance is clear for its intended cleanup scenario.

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