adb_qemu_images

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

No annotations provided; description only lists actions without disclosing side effects (e.g., deletion permanence), permission requirements, or error handling. For a mutation tool, more behavioral detail is necessary.

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 front-loading purpose and actions. No redundant information; 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?

Covers main actions and storage location but omits return value description (especially for list), error conditions, and differentiation from siblings. Adequate but not fully complete for an agent.

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 covers all parameters with descriptions. Tool description adds 'Images stored in DeepADB image directory' but does not significantly enhance parameter understanding beyond schema. Baseline 3 for 100% coverage.

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?

Description clearly states manage QEMU disk images, lists three actions (list, create, delete), and specifies storage location. It distinguishes from sibling tools like adb_qemu_start/stop/connect by focusing on image lifecycle.

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?

Implicitly suggests use for image management but lacks explicit guidance on when to use this vs. other QEMU tools (e.g., adb_qemu_setup). No when-not-to-use or alternatives mentioned.

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