as_avd_stop

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds that it uses 'adb emu kill' and returns JSON output, but does not elaborate on side effects (e.g., behavior if emulator already stopped) or safety beyond annotations. It adds some context but not substantial.

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: two short sentences plus bulleted Args/Returns. Every sentence provides necessary information without redundancy, making it efficient for an agent to parse.

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 parameter, annotations, and an output schema, the description covers purpose, parameter, and return type. It lacks explicit mention of behavior when no emulator is running or confirmation of idempotency, but these are partially covered by annotations. Overall, it is sufficiently complete for its complexity.

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?

The input schema already provides a detailed description for the 'serial' parameter, including format and default behavior. The tool description merely restates 'optional serial (else the first running emulator)' without adding new semantic meaning. With high schema coverage, baseline score 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 verb 'stop' and the resource 'running emulator', with the parenthetical '(adb emu kill)' providing implementation detail. It distinguishes from sibling tools like as_avd_start, as_avd_list, and as_avd_delete, which have different actions.

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 implies usage for stopping an emulator and mentions optional serial filtering, but does not explicitly state when to use this tool vs. alternatives (e.g., as_avd_delete for removal). No exclusions or when-not-to-use guidance is provided.

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