List WebView pages

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

The readOnlyHint annotation already declares this is a safe read. The description adds real behavioral value beyond that: it scopes the result set (WebView/Chrome pages on connected devices) and discloses the shape of what comes back (a target id per page for attach). It stops short of covering failure modes like no connected devices.

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 tight sentences, front-loaded with what gets listed and followed by the one fact an agent needs next (the returned target id feeds attach). 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?

For a zero-arg listing tool with an annotation covering its safety profile, this covers purpose, scope, and the handoff to attach without an output schema. Minor omissions (empty-result behavior, whether filtering exists) do not block correct invocation.

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 the schema imposes no burden; the baseline for a no-param tool is 4. The description appropriately says nothing about arguments rather than padding with irrelevant detail.

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?

States a specific verb ('List') and a precise resource ('debuggable H5 pages running inside Android WebViews (and Chrome) on connected devices'), and it names the follow-up sibling action ('pass to attach'). An agent can distinguish this from attach/detach/evaluate_js immediately.

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 makes the usage context clear implicitly by tying the output to the 'attach' step, so an agent knows to call this before attaching. It does not state when-not to use it or mention alternatives, keeping it short of full explicit routing.

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