List targets

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

No annotations, so the description carries the burden. It usefully warns that stale pages from earlier reloads appear in results — a genuine behavioral caveat that prevents the agent from assuming duplicates are bugs. However, it says nothing about failure modes when Metro is unreachable, ordering, or whether the call is cheap/safe to repeat.

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?

Two sentences, front-loaded with the action, with the parenthetical carrying only genuinely clarifying content. Nothing is redundant and nothing needs trimming.

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?

With no output schema and no annotations, the description does the important work of explaining what comes back (targets, including several per device, and a target_id to feed connect). Missing only the preconditions for calling it and any hint of the result shape beyond target_id.

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?

Zero parameters, so the baseline is 4; the schema has nothing to explain. The mention of target_id is not a parameter but an output-field hint, which adds value in the absence of an output schema.

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 every debuggable React Native target Metro exposes') with a clarifying parenthetical that defines what a target is and why one device can yield several. It implicitly distinguishes itself from list_devices by noting targets live behind Metro, though it never names that sibling explicitly.

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?

'Pass a target_id to connect' establishes the downstream relationship to the connect tool, which is real routing guidance. But there is no explicit when-to-use or prerequisite statement (e.g., must Metro already be reachable? call list_devices first?), leaving the agent to infer the workflow.

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