adb_emulator_stop

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

With no annotations provided, the description carries the burden. It reveals the use of a graceful shutdown method, but does not disclose what happens if the emulator is not running, whether the call blocks, or any side effects.

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 extremely concise, consisting of two short sentences with no extraneous information. Every word serves a purpose.

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 stop action, the description is mostly adequate, but it lacks details on parameter interaction (e.g., precedence when both avdName and device are provided) and does not specify return behavior or error conditions.

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?

Since schema description coverage is 100% and both parameters are clearly described in the schema, the tool description does not need to add parameter-specific info. It appropriately leaves parameter details to the schema.

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 verb 'Stop' and the resource 'a running emulator', making the tool's purpose unmistakable. It is distinct from sibling tools like 'adb_emulator_start' and 'adb_qemu_stop'.

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?

The description mentions the command used ('adb emu kill') for graceful shutdown, hinting at appropriate usage, but it lacks explicit guidance on when to use this tool versus alternatives, such as when to prefer avdName over device, or prerequisites like the emulator must be running.

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