android_launch_app

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

Does not disclose potential side effects, such as bringing an app to foreground, error conditions when app is missing, or any implications of the destructiveHint annotation; description is minimal.

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?

One sentence, no redundant wording, perfectly sized.

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?

Sufficient for a simple launch action, but lacks any mention of expected behavior or error handling; still, it's clear enough given the sibling context.

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 description clarifies that packageName must be an exact package name, supplementing the schema's regex pattern; however, it doesn't explain why the regex is structured that way.

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?

Clearly states the action (open), the target (installed application), and the criterion (exact package name), distinguishing it from URI-based opening tools.

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?

Provides no explicit guidance on when to choose this tool over alternatives like android_open_uri or android_apps; the only implicit hint is the requirement of an exact package name.

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