Install Android APK

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds one piece of behavioral context — that the APK is read from the local workspace — but is silent on replace semantics, permission granting, and device selection.

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 tight sentence with no filler and the key action front-loaded. It is efficiently written, though brevity here is partly the product of under-specification rather than deliberate editing.

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 7-parameter mutation tool with no output schema and no annotation-level parameter help, the description is far too thin. An agent cannot tell how to pick among the device-identifier parameters or what replace/grantPermissions do.

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 0% across 7 parameters, so the description must carry the burden and does not. Only apkPath is obliquely referenced; the three overlapping device selectors (serial, deviceId, deviceName), replace, grantPermissions, and timeoutMs are entirely unexplained.

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 (Install) and resource (APK) and pins the source to the local workspace. It is clearly distinguishable from adb_uninstall, though it does not explicitly name siblings or what differentiates it from adb_push/adb_shell.

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?

No when-to-use guidance, no prerequisites, and no mention of which device is targeted when multiple devices are attached. It never says when NOT to use it or which alternative (adb_push, adb_shell) applies instead.

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