adb_qemu_stop

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

Without annotations, the description reveals behavior: sends SIGTERM with force kill option. It does not disclose side effects or prerequisites, but covers the core mechanism.

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 sentences, direct and efficient. Every word contributes to understanding without redundancy.

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 fails to mention the dual behavior when 'name' is omitted (lists running VMs instead of stopping). This is a significant gap for 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 coverage is 100% with clear parameter descriptions. The description only adds a brief paraphrasing of the force option, providing no significant additional meaning beyond 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 'Stop a running QEMU virtual machine', providing a specific verb-resource pair that distinguishes it from sibling tools like adb_qemu_start or adb_emulator_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 explains the shutdown mechanism (SIGTERM vs SIGKILL) but does not explicitly mention when to use this tool over alternatives or any prerequisites.

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