adb_build_and_install

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

No annotations are provided, so the description carries full burden. It discloses only that it builds a debug APK and installs it. It does not mention side effects (e.g., overwriting previous APK), required permissions, build tool dependencies, or potential failures. Critical behavioral traits are 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 a single concise sentence that conveys the core purpose. It is front-loaded with the essential action. While it is very brief, it contains no extraneous information. Could be slightly more structured but earns a 4 for efficiency.

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 annotations, no output schema, and only two parameters, the description is insufficiently complete. It does not explain return values, error conditions, how to verify installation success, or any configuration details (e.g., debug variant, build system). The tool performs a significant combined operation but lacks context for safe use.

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 (projectPath and device), achieving 100% coverage. The description adds no additional meaning beyond what is in the schema. Baseline 3 is appropriate since schema does the heavy lifting.

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 it builds a debug APK and installs it, calling it a 'convenience wrapper'. This distinguishes it from sibling tools like adb_install (which installs an existing APK) and adb_install_bundle (which installs a bundle). The verb 'build and install' is specific and the resource is a debug APK.

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 no explicit guidance on when to use this tool vs alternatives like adb_install or adb_gradle. It mentions 'convenience wrapper' but does not specify prerequisites (e.g., connected device, Android build setup) or when not to use it (e.g., for release builds). This leaves ambiguity.

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