frida_android_port_forward

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

No annotations exist, so the description bears full burden. It mentions 'with adb' but does not disclose side effects (e.g., overwriting existing forwards), prerequisites (adb installed, device connected), or error states. Lacks sufficient behavioral detail.

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 very concise (12 words) but overly brief. It lacks structure (e.g., no sections) and omits critical information. While every sentence earns its place, it does not fulfill the tool's informational needs.

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, the description should explain return values or outcomes. It does not. Also missing prerequisites and restrictions. For a straightforward tool, it is incomplete for an AI agent to use correctly.

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 description coverage is 0%, and the description does not explain any parameters. It vaguely refers to 'local TCP port' and 'Android device TCP port' but does not map them to local_port and remote_port. The adb_serial parameter is completely ignored. Fails to add meaning 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 verb 'Forward' and the resource 'local TCP port to an Android device TCP port with adb'. It effectively distinguishes from sibling tools like list and remove by specifying the action of creating a forward.

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 does not explicitly state when to use this tool versus alternatives like frida_android_port_forward_list or frida_android_port_forward_remove. Context suggests it's for creating a forward, but no direct guidance is provided.

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