apk_preview_launch_app

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

The description states the concrete behavior: launching the main activity of an installed package. The annotations already indicate this is not read-only and not destructive, so the description adds the target-specific behavior without contradicting the annotations.

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 short sentence with no filler, making it easy to parse and front-loaded. It could be slightly more informative, but it does not waste any words.

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 one-parameter tool with an output schema and annotations, the description covers the basic operation. However, it does not mention prerequisites such as an active session or that the package must already be installed, which would help an agent plan the correct sequence of calls.

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?

The schema provides no description for the 'package' parameter, and schema coverage is 0%. The description only casually mentions 'installed package' and does not explain the expected format, the need for a full package name, or how to discover valid package values.

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 identifies the action ('Launch') and the resource ('installed package main activity'), making the tool's purpose immediately understandable. It is distinct from siblings like install_apk or list_apps, though it does not explicitly compare itself to them.

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 guidance on when to use this tool versus alternatives, such as listing available packages first or installing the package if it is not present. The phrase 'installed package' implies a prerequisite but does not state it explicitly or point to a sibling tool.

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