install_apk

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

Annotations already indicate a destructive, non-read-only operation. The description adds valuable behavioral context by constraining the APK to be within the session root or ADB_APK_ROOT, and clarifies the fallback behavior when no session root is set. This goes beyond the safe-read baseline and discloses path restrictions.

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, front-loaded sentence with no filler. It conveys the core action and key constraint efficiently, earning its place without redundancy.

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 five parameters with full schema descriptions and the destructive annotation, the description is adequately complete. It covers purpose and location restrictions, while device selection and permission handling are already documented in the schema. The lack of an output schema reduces the need for return-value narration.

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?

With 100% schema coverage, the baseline is 3. The description adds meaningful semantics for apk_path by requiring it to be contained within the session root or ADB_APK_ROOT, which is not stated in the schema's apk_path description. This enriches the 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 action ('Install an APK') and specifies the resource scope (APK within the active session project root or ADB_APK_ROOT). This distinguishes it from sibling tools like uninstall_app, launch_app, or run_build, making the 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 provides clear context by specifying where the APK must be located and the fallback root when no session root is set. It does not explicitly mention alternatives or when-not-to-use, but the context is sufficient to guide the agent on when this tool is appropriate.

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