adb_install

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

No annotations are provided, so the description must fully disclose behavioral traits. It states 'Install an APK' which is a write operation, but it does not mention side effects (e.g., overwriting existing app, needing permissions, device state requirements) beyond what the input schema already conveys through parameters like 'replace' and 'downgrade'.

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 a single, concise sentence that front-loads the action. It contains no unnecessary words, but is slightly too brief to be fully informative.

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 has 4 parameters, no output schema, and no annotations, the description is incomplete. It fails to mention prerequisites (e.g., device connected, APK path validity), return values (e.g., success/failure), or what happens if the APK is already installed.

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 100% for all 4 parameters. The description adds minimal value beyond the schema by reiterating 'Provide the full local path' for 'apkPath', which is already clear from the schema. No additional context is given for other parameters.

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 action ('Install an APK') and the target resource ('on the device'). Among siblings, there are distinct tools like 'adb_install_bundle' for bundles and 'adb_build_and_install' for building then installing, making this tool's purpose 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 (you need a local APK path) but does not specify when to use this tool over alternatives like 'adb_install_bundle' or 'adb_build_and_install'. No explicit when-not or exclusion criteria are provided.

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