List devices

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

No annotations are provided, so the description carries the full burden. It adds useful scope ('connected' only) and hints at return content ('their state'), implying a read-only enumeration, but never states that 'state' means the adb device status (device/offline/unauthorized) or whether unequipped/emulator devices are included.

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?

One short sentence, front-loaded with the verb and resource, with zero filler. Nothing in it is redundant with the title in a wasteful way.

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 trivial zero-param read tool this covers the essentials, but with no output schema the ambiguous term 'state' is left unexplained — the agent cannot know which status values to expect or how to interpret an 'unauthorized' or 'offline' device before calling.

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 takes zero parameters, so there is nothing for the description to disambiguate against the empty schema; baseline 4 applies. The description correctly refrains from inventing filter arguments.

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?

Specific verb+resource: 'List connected adb devices and their state.' An agent immediately knows this is an enumeration of attached devices. It does not, however, distinguish itself from the sibling device_info tool (per-device detail), leaving that inference to the agent.

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?

There is no when-to-use guidance, no mention of alternatives (device_info for per-device detail), and no preconditions stated. The agent must infer from the name alone that this is the discovery step before calling device_info or screenshot.

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