adb_multi_install

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

No annotations provided, so the description must fully disclose behavior. It mentions parallel execution but omits critical details like failure handling (e.g., if some devices fail), output format, or whether the operation is synchronous. This leaves significant behavioral gaps.

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 front-loads the core action and scope. It could benefit from slightly more detail (e.g., behavior without devices) but is not verbose.

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?

For a simple tool with no output schema, the description covers the basic function but lacks completeness about execution behavior (blocking vs async), error reporting, and result presentation (e.g., success/failure per device). More context is needed for reliable multi-device operations.

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% with clear descriptions for all three parameters (apkPath, devices, replace). The tool description adds no additional parameter context, but the schema itself is adequate, justifying the baseline score of 3.

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 installs an APK on multiple or all connected devices in parallel. It uses specific verbs and resource, and implicitly distinguishes from single-device install tools like adb_install, but does not explicitly differentiate from siblings like adb_install_bundle.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., adb_install for single device, adb_install_bundle for split APKs). The description lacks context about prerequisites or conditions for using parallel install.

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