Install Android APK

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

Annotations already indicate it is not read-only and not destructive. The description adds 'bounded timeout and structured ADB result', which provides useful behavioral context beyond the annotations, but does not elaborate on side effects or required permissions.

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 sentence of 9 words, front-loading the action. It is efficient but may be overly brief for the level of detail needed.

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 the 3 parameters, low schema coverage, and existing annotations, the description lacks completeness. It does not explain the role of 'replace', the necessity of 'serial', or the nature of the structured result, leaving gaps for an agent.

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?

With schema coverage at only 33%, the description should compensate but fails to add meaning. It only implies that 'path' is for a local APK, but does not explain 'replace' or the significance of 'serial'. The serial description in the schema is already present.

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 action (Install), the resource (one local APK), and adds distinguishing details (bounded timeout, structured ADB result). This differentiates it from siblings like mobile_app_launch and mobile_app_uninstall.

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 use for installing an APK but does not provide explicit guidance on when to use this tool versus alternatives, nor does it state when not to use it. The context is implied from the purpose.

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