list_android_devices

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

With no annotations, the description carries the full burden of disclosing behavior. It states the operation is a list (read-only) but does not mention whether the ADB server is started, the format of the output, or any side effects. For a simple list tool, this is minimal but sufficient; it adds the context of the specific ADB binary, which is useful.

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 with no wasted words. The verb 'List' is front-loaded, and the qualifier 'ADB bundled with AirtestIDE' is precise and necessary. Perfectly concise.

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 tool with an empty input schema and an existing output schema, the description adequately covers the tool's purpose and scope. It does not detail the return values, but the output schema is expected to provide that. The only minor gap is the lack of mention of any side effects like starting the ADB server, but this is not critical for a list operation.

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 schema is trivially covered. The baseline for 0-parameter tools is 4, and the description correctly does not attempt to explain parameters. No additional parameter semantics are needed.

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' with a clear resource 'Android devices' and a qualifier 'visible to the ADB bundled with AirtestIDE', making the tool's purpose unambiguous. It distinguishes itself from sibling action-oriented tools like touch, swipe, and start_app by being a discovery/list operation.

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 provides clear context by specifying the ADB source (bundled with AirtestIDE), which is relevant for when the tool should be used. It does not explicitly mention alternatives or exclusions, but none of the sibling tools serve a similar listing function, so the guidance is adequate.

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