List pages

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

The annotation already declares readOnlyHint: true, so the safe read nature is clear. The description adds valuable context about output format (array of objects with id, url, title, name) and mentions both named pages and tabs. No contradictions exist between description and annotations.

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?

The description is a single, front-loaded sentence. It states the action, the resource, and the output structure without any waste. Every word earns its place.

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?

Given readOnlyHint annotation, good schema coverage, and no output schema, the description adequately covers the tool's purpose and output shape. However, it doesn't mention pagination limits, whether the list includes all frames or just main frames, or what happens when no pages exist. For a simple list tool, this is minimally complete but not thorough.

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 each of the 5 parameters is well-documented in the schema alone. The description adds no additional parameter-level insight beyond what the schema provides. Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly uses the verb 'list' and resource 'named pages and open browser tabs', and gives the output structure ID, url, title, name. This distinguishes it from siblings like dev_browser_run, dev_browser_page_open, and dev_browser_snapshot. However, it does not explicitly say it returns all pages/tabs for the current browser instance, so purpose is clear but not maximally precise.

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 provides no information about when to use this tool versus alternatives. In a large sibling set (15 tools) with many similar operations (e.g., dev_browser_page_open, dev_browser_close_page, dev_browser_snapshot), explicit guidance on when to list vs. open/close/snapshot would be valuable. There are no prerequisites, exclusions, or comparisons mentioned.

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