Installs a local APK file onto a connected Android device, optionally replacing an existing app of the same package.
将本地 APK 文件安装到已连接的 Android 设备。
| Name | Required | Description | Default |
|---|---|---|---|
| apk_path | Yes | 本地 APK 文件的绝对路径，例如 /Users/xxx/app.apk。 | |
| replace_existing | No | 是否替换已安装的同包名应用，默认 True。 |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral burden. It states the action and target device, but does not disclose mutation side effects, permission requirements, error behavior, or what happens when replacing an existing app.
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?
One efficient sentence, front-loaded with the action and target. No wasted words or redundant clauses.
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?
An output schema exists and parameter schema coverage is complete, so return values and parameters need not be explained. The description covers the core action and target, though it could mention more prerequisites or side effects given the absence of annotations.
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 100%, so the schema already fully documents both apk_path and replace_existing. The description adds no additional parameter meaning; 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?
Specific verb '安装' (install) and resource '本地 APK 文件' (local APK file) with target '已连接的 Android 设备' (connected Android device). Clear what it does, but it does not explicitly differentiate from siblings like push_file.
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 when-to-use guidance, no alternatives, no prerequisites. Usage is only implied by the tool name and the action described.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.