Install APK

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

Annotations only declare destructiveHint=false, so the description carries extra weight, and 'reinstall, keeping data' usefully explains why the operation is non-destructive and what happens to existing app data. It doesn't mention failure modes or permission requirements beyond the grantPermissions flag, leaving a small gap.

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?

Two tight sentences, zero waste, with the core action and its data-retention behavior front-loaded before the sibling pointer. Every sentence earns its place.

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?

No output schema exists, but this is a straightforward side-effecting action with a small, mostly documented parameter set; the description covers purpose and the APK-discovery path. Minor gaps (allowDowngrade meaning, serial requirement) are left to the schema.

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 75%, with most parameters (serial, apkPath, grantPermissions) already documented in the schema; only allowDowngrade lacks a description. The description adds no parameter-level detail, so the 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?

States a specific verb (install/reinstall) and resource (APK on a device), and adds the useful nuance that a reinstall keeps data. An agent can distinguish this from siblings like app_uninstall or app_launch without opening a schema.

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?

'Use project_apks to find built APKs' explicitly routes the agent to the sibling that supplies the required apkPath. However, there is no guidance on when not to use this tool or how it relates to app_launch/app_uninstall, so it stops short of full when/when-not coverage.

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