adb_install_bundle

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the action without detailing side effects, prerequisites, or failure modes. For example, it does not mention that `replace` defaults to true or what happens on version mismatch. This is a significant gap for a mutation tool.

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 sentences, no redundancy, and front-loaded with the core action. Every word contributes to clarity without excess. Ideal conciseness.

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 no output schema and no annotations, the description covers the main purpose but omits details about the `device`, `replace`, and `allowDowngrade` parameters. While schema documents them, the description could provide context (e.g., when to set `replace` to false). The description is adequate for a simple install tool but not fully comprehensive.

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 100%, so baseline is 3. The description adds value by explaining that `apkPaths` should include base APK plus config splits (language, density, ABI), which clarifies the expected input beyond the schema. This enriches parameter understanding.

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 tool installs multiple APK splits (app bundle) using `install-multiple`, implicitly distinguishing it from sibling tools like adb_install (single APK) and adb_multi_install (likely multiple separate APKs). The verb 'install' and resource 'multiple APK splits' are specific and unambiguous.

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 indicates when to use the tool: when you have split APK files (base + config splits). While it does not explicitly list alternatives or exclusions, the context is clear for an agent familiar with APK installation. The mention of 'app bundle' directly ties to common use cases.

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