adb_start_app

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

Description mentions it resolves the default launcher activity, which adds some behavior beyond the basic launch. However, no annotations are provided, and the description does not disclose error handling, prerequisites (like app installed), or return values for such a simple tool.

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?

Single sentence, concise and front-loaded, no wasted 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?

Tool is simple with 2 parameters and no output schema. Description covers purpose but lacks details on error behavior, return values, or usage nuances. Adequate but not complete.

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 100% with both parameters described. The description adds context about default launcher activity resolution but does not add new meaning beyond what the schema already provides.

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?

Description uses specific verb 'Launch' and resource 'app by package name', and clarifies it resolves the default launcher activity. This distinguishes it from sibling tools like adb_start_activity and adb_restart_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?

Implies usage when wanting to launch an app by package name, but provides no explicit guidance on when to use this tool versus siblings like adb_start_activity for specific activities or adb_restart_app for restarting.

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