install_apk

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

With no annotations, the description carries the full burden. It usefully maps the boolean flags to their adb equivalents (replace=-r, grant_permissions=-g, downgrade=-d) and states the return shape, which is real behavioral value for a mutation tool. It still omits whether replacement destroys existing app data, permission requirements, and failure modes.

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, front-loaded with the core action and the multi-APK conditional, followed by compact flag mappings and return shape. No waste.

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?

An output schema exists, so explaining {status, message} is redundant but harmless. For a 5-parameter mutation tool with zero annotation coverage and zero schema descriptions, the definition is still thin on the serial/path parameters and side effects on existing installs.

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 0%, so the description must compensate. It explains the meaning of replace, grant_permissions, and downgrade via adb flag equivalents, but leaves serial and apk_paths (including path format and whether multiple paths mean split APKs) undefined, so it only partially fills the gap.

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+resource ('Install an APK') and additionally clarifies a distinct mode ('split-APK set via install-multiple when >1 path given'). It does not name or contrast with siblings, but the purpose is unambiguous and install has no close sibling.

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?

Provides one conditional rule: use the multi-APK path when more than one path is given. It does not address when to use this versus uninstall/reinstall workflows, prerequisites (device connection, serial resolution), or failure/retry guidance, so usage is implied rather than fully guided.

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