adb_restart_app

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

Without annotations, the description accurately conveys the two-step behavior and single-call convenience, though it omits potential side effects like clearing app state from force-stop.

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?

Two succinct sentences deliver the core purpose and benefit without any 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?

For a straightforward action tool, the description is complete enough, though it does not explain the output or behavior after relaunch.

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%, so the description adds no parameter meaning beyond what is already documented; the default delay (500ms) is not mentioned.

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 states the action (force-stop then relaunch) and the resource (an app), distinguishing it from siblings like adb_force_stop or adb_start_app by combining both steps.

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?

It implies usage for debugging workflows, but does not explicitly state when to avoid it or mention alternatives like separate stop/start.

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