adb_install

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. Installing an APK is a significant mutating operation that could modify/replace existing apps, require signature validation, or fail due to version conflicts. None of these behaviors are disclosed. The description is purely functional with zero behavioral context about what happens to the device or existing state.

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 sentence that communicates the essential purpose with zero waste. There is no filler, no redundancy, and the structure is clean. Being concise is appropriate here given the simplicity of the tool.

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?

For a mutating tool (installing software onto a device) with no annotations and no output schema, the description should provide more context. It doesn't mention what success looks like, what errors might occur, whether this replaces existing installations, or any device compatibility requirements. The tool complexity is moderate (2 params, 1 required), but the mutating nature and lack of structured metadata warrant a richer description.

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 50% — apk_path has no schema description while serial does ("device serial (host:port); omit if only one device"). The tool description clarifies that apk_path is a local file path, adding meaning beyond the bare schema property. However, it doesn't explain path format requirements, supported file types, or the relationship between apk_path and serial. Marginal value added over the schema.

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 "Install an APK from a local file path onto the device" uses a clear verb (Install) with a specific resource (APK) and scope (from local file path onto device). It clearly distinguishes from siblings like adb_push (which transfers files) and adb_uninstall (which removes apps). It doesn't explicitly call out the sibling distinction, but the purpose is 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 implies usage: use when you want to install an APK that exists at a local file path. However, there's no explicit when-to-use or when-not-to-use guidance, no mention of alternatives like adb_push-then-install, and no mention of prerequisites such as package compatibility or the serial requirement for multi-device setups. It's adequate but relies on the agent to infer context.

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