as_adb_install

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

Annotations include readOnlyHint=false, destructiveHint=false, and openWorldHint=true, indicating a non-read-only, non-destructive, externally visible operation. The description adds that the return is a JSON string with install result, but does not disclose side effects (e.g., device state changes) beyond annotations. No contradiction with annotations.

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 concise, starting with the core action, listing parameters, and stating return format. It is front-loaded and avoids unnecessary detail. Slight improvement could be achieved by removing the 'Args' repetition, but overall efficient.

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 tool's moderate complexity, an output schema exists, and annotations cover behavioral hints, the description is reasonably complete. It states the action, parameters, and return type. Missing error handling or side effects, but not critical for this straightforward install tool.

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?

The description lists parameters (apk_path, serial, reinstall, allow_downgrade, grant_permissions) but the schema already provides detailed descriptions for each sub-property. With high schema coverage, the description adds marginal value. It does not clarify parameter syntax or relationships.

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 'Install an APK onto a device/emulator,' specifying the verb and resource. It is distinct from sibling tools like as_aab_install (which installs AAB) and as_adb_uninstall, though it does not explicitly differentiate them. The name itself clarifies the target.

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 provides no guidance on when to use this tool versus alternatives like as_aab_install or as_adb_uninstall. It lacks prerequisites, context, or scenarios for use. Users must infer usage from the name alone.

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