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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered. The description adds real context beyond that: the endpoint is loopback-only, it enumerates debuggable Chromium pages, and the returned target_id/title/url feed subsequent browser calls. It omits failure modes (no browser running, connection refused), which keeps it at 4.

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, zero waste, front-loaded with the usage condition followed by the mechanics and the downstream payoff. Nothing redundant with the schema or annotations.

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?

An output schema exists, so return values need not be spelled out, and the description correctly points at what to do with them. For a 6-param discovery tool it is nearly complete; only error/timeout behavior is unaddressed.

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?

Schema description coverage is 100%, so the schema already documents title/device/endpoint/target_id/timeout_ms/url_contains. The description only alludes to target_id/title/url as return values, adding no filtering syntax or default behavior beyond the schema. Baseline 3 applies.

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 (lists) and resource (debuggable Chromium pages) plus the scope of the source (loopback-only CDP endpoint). An agent can distinguish this from siblings like browser_snapshot or browser_new_tab purely from the description.

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?

Explicitly gives the triggering condition: 'when starting CDP browser automation and the target page or tab is not already unambiguous,' and explains that the returned ids scope later browser tools. It doesn't name competing tools (e.g. browser_find, browser_new_tab) or exclusions, so it stops short of a 5.

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