as_adb_start_app

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

Annotations already indicate the tool is not read-only and open world. The description adds minimal behavioral context beyond the mechanism ('via monkey launcher intent') and does not disclose side effects, error cases, or state changes.

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 efficient: three lines with a clear purpose statement, args summary, and return type. No fluff or 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?

For a simple launch tool, the description covers input and return format adequately. However, it lacks details on error handling, behavior when app is already running, or prerequisites (e.g., device availability).

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 adds value by explaining the two methods (component vs package) and the default launcher behavior, which complements the schema's property descriptions. Schema descriptions cover the fields well, so the description provides extra context on usage.

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 'Launch an app by component or by package (via monkey launcher intent)' with a specific verb and resource, clearly distinguishing it from siblings like as_adb_stop_app.

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 or when-to-avoid guidance is provided. Alternatives such as as_run_app are not mentioned, leaving the agent without context for tool selection.

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