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 clearly explains that it lists only connected Android ADB devices and configured iOS Appium devices, and that the output contains device serials. The read-only nature is implied by 'List' but not explicitly stated; however, for a listing tool this is adequate.

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 exactly two sentences, front-loaded with the verb 'List,' and every word earns its place. It states what it lists and why to call it first, with no filler.

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's simplicity (zero params, output schema exists), the description is complete. It explains the tool's purpose, the scope of devices, and the key output detail (device serial) needed for subsequent operations. The presence of an output schema means return-value details are already documented elsewhere.

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 need not explain parameters, and it doesn't, which is appropriate. The empty schema is fully covered, and the description adds no parameter-related confusion.

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 the tool lists connected Android ADB devices and configured iOS Appium devices, with a clear verb and resource. It distinguishes itself from sibling tools by being the device-listing entry point, explicitly saying to call it first to get the device serial needed for other tools.

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 gives clear contextual guidance: 'Call this first' indicates when to use it as a prerequisite for other tools. It does not explicitly mention when not to use it or name alternative tools, so it stops short of a 5, but the 'call this first' instruction is strong usage guidance.

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