Install Android APK

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, openWorld=true, so the safety profile is covered. The description usefully adds that the operation is timeout-bounded and returns a structured ADB result, but says nothing about failure behavior, whether a live device session is required, or what 'replace' does to existing installs.

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 front-loaded sentence with no filler; the core action and its constraints come first. It is arguably under-specified rather than over-long, but the structure itself is efficient.

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?

With an output schema present, explaining the return value is unnecessary, and the bounded-timeout note is useful. However, for a 3-parameter mutation tool at 33% schema coverage it leaves the 'replace' semantics and the local-device prerequisite unaddressed, so it is only minimally sufficient.

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 only 33%, so the description must compensate and largely does not. It clarifies that 'path' is a local APK, but adds nothing about 'replace' (default true) or about the timeout it mentions having no corresponding parameter. 'serial' is documented in the schema, not the description.

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 states a specific verb and resource ('Install one local APK') and adds scope constraints ('local', 'one', 'bounded timeout', 'structured ADB result') that separate it from mobile_app_launch, mobile_app_uninstall, and mobile_app_inspect. It stops short of naming a sibling condition explicitly, so the differentiation is inferable rather than stated.

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?

There is no when-to-use guidance: nothing says to install only when the app is absent, nor routes the agent to mobile_app_launch for already-installed apps or mobile_app_uninstall for removal. The only implicit signal is 'local APK', which hints at a prerequisite but not a decision rule.

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