adb_reverse

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

No annotations are provided, so the description carries the full burden. It explains the core behavior (forwarding a port) and warns about silent fallback in React Native development. However, it does not disclose what happens if the forward already exists, error handling, or required permissions. This is adequate but not complete.

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 two sentences plus a final clause, all contributing useful information. It is slightly verbose but not overly long. The key points are front-loaded (purpose, canonical use) and then warning and parameter note follow.

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 no output schema and no annotations, the description is fairly complete. It covers the purpose, usage context, key parameter (remove), and even references a related tool (app_state). It does not describe return values, but that is acceptable without an output schema.

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 100%, so the baseline is 3. The description adds context: 'canonical use is tcp:8081 for Metro' for device_port and mentions remove=true behavior. However, it does not add significant meaning beyond the schema descriptions, which already cover all parameters.

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 forwards a DEVICE TCP port to a HOST port (adb reverse). It specifies the canonical use case (tcp:8081 for Metro), distinguishing it from other adb tools like list_devices or logcat. The verb 'forward' and resource 'TCP port' are explicit.

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 explicitly says this is 'CRITICAL for RN/Expo dev clients' and explains when to use it (before a dev-client session) and what to suspect if edits have no effect. It also mentions the remove parameter to undo the forward. It does not explicitly state when not to use it, but the context is clear.

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