List targets

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

With no annotations, the description carries the full burden. It usefully discloses that device enumeration is 'best-effort' (i.e., may be incomplete or fail), which is real behavioral context, and the read-only 'Show' framing implies no mutation. It stops short of saying whether the call requires a live Appium server, what happens when none is configured, or how failures surface.

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?

A single well-formed sentence with the primary payload (the configured connection) front-loaded and the secondary, less reliable part (attached devices) qualified. No filler, though the parenthetical enumeration makes it slightly dense.

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?

No output schema exists, so the description must convey return values — and it does, naming the three connection fields and the device list. Combined with the 'best-effort' caveat, an agent knows enough to call it; only failure/precondition behavior is unstated.

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. Baseline 4 applies; the description correctly implies a no-argument call.

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 names a specific verb ('Show') and enumerates exactly what is returned: the Appium connection URL, target UDID, default bundle ID, plus attached devices/simulators. That makes the output concrete, though it doesn't explicitly contrast with the similar-sounding sibling device_info, so the boundary between the two needs inference.

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 and no mention of alternatives. An agent facing both list_targets and device_info has no textual basis for choosing one over the other.

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