adb_farm_run

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

No annotations provided, so the description bears full responsibility. It describes the upload and execution behavior but omits important details such as potential costs, destructive actions, whether results are stored, or impact on Firebase project. The prerequisite is noted but broader behavioral context is missing.

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 three sentences covering purpose, behavior, and requirements. It is front-loaded and efficient, though it could be more structured by separating action from prerequisites.

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's complexity (Firebase Test Lab test runner, 7 params, no output schema), the description provides adequate purpose and basic behavior but lacks detail on output (e.g., result location), blocking behavior, cost implications, or long runtime considerations. Additional context would improve completeness.

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 baseline is 3. The description does not add significant meaning beyond the schema parameter descriptions; it merely reiterates the overall purpose. No additional context for parameters like resultsBucket or execTimeoutMs.

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 runs tests on Firebase Test Lab with APK upload and execution across devices. It effectively communicates the primary action and resource, but does not explicitly distinguish from sibling tools like adb_farm_results or adb_farm_matrix.

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 mentions the prerequisite of authenticated gcloud CLI with a Firebase project, but provides no guidance on when to use this tool versus alternatives, nor when not to use it. No comparative context with siblings.

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