apk_preview_install_apk

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

Annotations already indicate this is a mutating operation (readOnlyHint=false) and not destructive. The description adds the useful scoping details that it installs or replaces an APK on an active emulator, but does not disclose side effects such as whether existing app data is cleared or whether a session must be started first.

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?

A single, front-loaded sentence with no filler. Every word contributes to understanding the action, target, and context.

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?

With one parameter, an output schema, and annotations covering read-only/destructive aspects, the description covers the essential action and prerequisite. It could add explicit 'run after apk_preview_start_session' guidance, but 'active dedicated emulator' sufficiently implies the required context.

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 0%, so the description must compensate. The phrase 'one local APK' clarifies that apk_path refers to a local file path, but it does not specify path form, required file extension, or constraints on the emulator side.

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 uses a specific verb ('Install or replace') and names both the resource ('one local APK') and the target context ('active dedicated emulator'). This clearly differentiates it from sibling tools like apk_preview_launch_app and apk_preview_list_apps.

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?

It explicitly scopes use to an active dedicated emulator and to a single local APK, giving clear contextual conditions. It does not name siblings or explicitly state when not to use it, but the intended context is evident from the wording and sibling list.

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