Select a browser page by ID to set the context for future DevTools tool calls; optionally bring it to the front.
Select a page as a context for future tool calls.
| Name | Required | Description | Default |
|---|---|---|---|
| pageId | Yes | The ID of the page to select. Call list_pages to get available pages. | |
| bringToFront | No | Whether to focus the page and bring it to the top. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint=true is already declared, so the safety profile is covered. The description usefully adds that selection affects future tool calls (context effect), but does not disclose what happens to the previously selected page or whether multiple contexts are allowed.
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 front-loaded sentence with no filler. Slightly terse rather than wasteful — nothing redundant, but also little added beyond the essentials.
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 simple 2-parameter, low-complexity tool with full schema coverage and no output schema, the definition is minimally sufficient. The 'context' concept and persistence across calls could be spelled out a bit more for an agent to use it confidently.
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%; pageId documents its role and even routes to list_pages, and bringToFront documents its effect. The description adds nothing beyond the schema, so the 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 (select) and resource (page) and adds the scope/purpose 'as a context for future tool calls', which distinguishes it from siblings like new_page, close_page, or navigate_page. It's clear what it does, though it doesn't explicitly name the distinguishing siblings.
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 implies usage (set a context for later calls), and the schema's pageId note points to list_pages for discovery. However, it doesn't say when to prefer this over navigate_page or new_page, nor whether it's required before other tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.