adb_test_gen_from_ui

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

No annotations are provided, so the description carries full burden. It states the tool taps elements, takes screenshots, and verifies no crash, but fails to disclose potential side effects like app state changes, requirements for screen state, or behavior on crash. Lack of transparency on these aspects.

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 concise, with two sentences that front-load the core purpose and output. No wasted words.

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?

The description covers the main functionality but lacks details on workflow structure, success/error conditions, and how to handle the output. For a tool generating complex output without an output schema, more completeness is expected.

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 schema already documents all 4 parameters. The description adds only the output format context ('Produces a workflow JSON compatible with adb_workflow_run'), which is helpful but does not enhance parameter semantics. Baseline 3 is appropriate.

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 analyzes the current screen, generates a test workflow with taps, screenshots, and crash verification. It distinguishes itself from siblings like adb_test_gen_from_intents and adb_tap_element by specifying the generation of a workflow JSON compatible with adb_workflow_run.

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 adb_test_gen_from_intents or adb_tap_element. It only implies usage by mentioning adb_workflow_run compatibility, but no when-to-use or when-not-to-use guidance is provided.

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