shutdown_emulator

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

No annotations are present, so the description carries the full burden. It reveals that the operation is a forceful 'adb emu kill', but does not disclose side effects (e.g., state saving, unsaved data loss) or expected response behavior. Some useful context is provided but more would be beneficial for a destructive action.

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 short sentences, front-loaded with the action and purpose. No wasted words; every sentence adds value.

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 tool is simple (one optional param, no output schema) and the description covers what it does and when to use it. However, given there are no annotations, a bit more about the impact of killing an emulator (e.g., losing unsaved state) would improve completeness.

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 description coverage is 100%, so the serial parameter is fully documented in the schema. The description does not add parameter-specific info, but the schema already explains when serial is optional. 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 explicitly states 'Power off a running emulator' with the underlying adb command in parentheses, making the action unambiguous. It clearly distinguishes from sibling tools like boot_emulator and 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?

Provides clear usage context: 'Use when you are done with a device you booted.' This implies ownership and timing, but doesn't explicitly contrast with other shutdown-like tools, though none are direct competitors.

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