list_emulators

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

The annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds value by specifying the exact scope of the listing (AVDs and connected devices), which is behavioral context beyond the annotation. It does not describe output format, but that is not a requirement given the simple nature and annotation coverage.

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 a single, concise sentence that front-loads the primary action ('List') and immediately specifies the targets. There is no redundancy or unnecessary detail.

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?

Given the tool has no parameters, no output schema, and a read-only annotation, the description is largely complete for a listing tool. It specifies what it lists. The only gap is the lack of detail about the output format (e.g., whether it returns names, paths, or details), but this is a minor omission for a simple list tool.

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?

There are zero parameters and the schema coverage is 100% (empty schema). Per rubric, the baseline for zero parameters is 4. The description does not need to explain parameters since none exist.

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 states a specific verb 'List' and clearly identifies the resources: available Android Virtual Devices (AVDs) and currently connected devices/emulators. This clearly differentiates from sibling tools like get_booted_serial or get_screen_info, which target specific devices or details.

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 its usage: to enumerate available devices. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusion criteria or when not to use it. The purpose is clear, but explicit guidance on alternatives is absent.

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