Install APKs on a connected Android device via adb; use reinstall to replace existing versions.
Install an APK on a connected device via adb.
| Name | Required | Description | Default |
|---|---|---|---|
| apkPath | Yes | ||
| reinstall | No | Pass -r to allow reinstalling over an existing install | |
| workspace | No | Workspace name (not id) - created automatically if it doesn't exist yet. Defaults to "default". | |
| deviceSerial | No |
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden of disclosing behavior. It only says 'install an APK', omitting important behavioral details like what happens if the app already exists, whether the installation is destructive to existing data, how device selection is determined, and what output or failure modes to expect.
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 front-loaded sentence with no filler. It states the verb and object immediately and stays appropriately short for a straightforward tool.
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 four parameters, no annotations, no output schema, and only 50% schema coverage, this description is not complete enough. It does not explain prerequisites like a connected device, how failures are reported, or the meaning of the workspace and deviceSerial parameters.
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 only 50%, and the description does not compensate. It adds no meaning for apkPath or deviceSerial, leaving the agent to guess whether apkPath is a local file path or a device path, and how deviceSerial is used to select among connected devices.
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 states a clear action ('Install') and a specific resource ('an APK on a connected device via adb'). It is easily distinguishable from sibling tools like build_apk, decompile_apk, adb_shell, and adb_devices.
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 implies the use case: install an existing APK on a connected device. However, it gives no explicit guidance about when not to use it, nor does it mention alternatives such as build_apk for building the APK first.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.