list_android_devices

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

With no annotations provided, the description carries the full burden. It discloses that the tool reads from adb ('visible to adb') and lists the specific device attributes. It does not hide any side effects (reading is safe) and provides enough context about behavior, though it could mention that it returns no devices if none are connected.

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 (13 words) that is front-loaded with the verb and resource, and includes all necessary information without any 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?

As a simple listing tool with no parameters and no output schema, the description adequately covers the purpose and return fields (serial, state, product, model). It could enhance completeness by describing the output format (e.g., list of dictionaries), but that is not critical for this 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?

The tool has zero parameters and the schema is empty, so the baseline is 4. The description does not need to explain parameters, and it correctly describes the output instead.

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 'List' and the resource 'Android devices visible to adb', with explicit output fields (serial, state, product, model). This distinguishes it from sibling tools like 'deploy_to_android' or 'get_android_preset_info', making the purpose unambiguous.

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 the tool is used when you need to see connected Android devices via adb, but it does not explicitly state when to use it versus alternatives, nor does it mention any prerequisites or exclusions. Usage context is inferred but not directly stated.

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