adb_list_devices

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the operation is a listing, which implies read-only behavior, but it does not disclose details such as whether the ADB server is started, what 'info' includes (e.g., serials, models), or how errors/empty results are handled. This is adequate for a simple read operation but lacks depth.

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 sentence, front-loaded with the action, and contains no extraneous words. Every word earns its place.

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?

This is a simple, zero-parameter listing tool. The description covers the essential purpose and output components ('status and info'). While it could slightly elaborate on what 'info' includes, the tool's simplicity means the current description is largely complete, especially given the absence of an output schema.

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 tool has zero parameters, so the baseline is 4. The description correctly avoids adding parameter information because there are no parameters to explain, and the schema already reflects this.

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 uses a specific verb ('List') and resource ('connected Android devices') and clarifies it includes 'status and info'. This clearly distinguishes it from sibling tools that operate on a specific device (e.g., adb_shell, adb_device_info).

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 discover connected devices—but does not explicitly state when to use it versus alternatives or mention that it should be used before other ADB commands. There is no explicit 'use when' guidance, only the implied context that it lists devices.

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