kill_emulator

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

No annotations provided, and the description 'Kill a specific Android Emulator' does not disclose behavioral traits such as whether it force stops or gracefully shuts down, side effects, or that it is destructive. The agent has no information beyond the name.

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 efficient as a single short sentence, but it lacks necessary detail. Conciseness should not sacrifice completeness; it earns a 3 for being non-verbose but insufficient.

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 tool with one required parameter and no output schema, the description is minimally complete in stating the action. However, it omits behavioral details and usage context, making it incomplete for safe and effective use.

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?

With 0% schema description coverage, the description must compensate but adds no meaning beyond the parameter name 'emulator_name'. No format hints or examples are given. The baseline of 3 is not justified because no parameter info is provided.

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 'Kill a specific Android Emulator' clearly states the action (kill) and the resource (Android Emulator). It distinguishes from sibling tools like start_emulator and list_emulators.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites like listing emulators first to obtain the name, or that killing stops the emulator process.

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