adb_emulator_stop

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

The description discloses the graceful shutdown method ('adb emu kill'), implying a safe operation. However, without annotations, it doesn't detail side effects (e.g., data loss if unsaved), required permissions, or behavior if emulator not running. Adequate but not thorough.

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 concise sentences with no filler. Action verb and method are front-loaded.

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?

The description lacks the nuance that omitting parameters lists running emulators instead of stopping. Without an output schema, the behavior for edge cases (e.g., nonexistent emulator) is missing. Adequate for a simple tool but could be more 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?

Input schema covers 100% of parameters with descriptions. The tool description adds no additional meaning beyond the schema. Baseline 3 is appropriate.

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 ('Stop'), the resource ('a running emulator'), and the method ('adb emu kill' for graceful shutdown). It distinguishes from siblings like adb_emulator_start.

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 explicit guidance on when to use this tool vs. alternatives (e.g., adb_disconnect or force stop). No prerequisites, exclusions, or when-not-to-use mentioned.

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