cdp_tabsList every open browser page through raw CDP to get a complete inventory of current tabs.
List EVERY open page in the browser (full inventory from raw CDP).
| Name | Required | Description | Default |
|---|---|---|---|
| port | No | CDP debug port (default 9222). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds modest context ('raw CDP', no filtering) but says nothing about return format, ordering, or how it differs from other CDP listing tools, so value beyond the structured fields is limited.
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 short sentence with the scope qualifier front-loaded and no wasted words. Nothing to trim.
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 zero-required-param listing tool with full annotation coverage and no output schema, the description is adequately complete. The only gap is any hint at return shape or how results relate to sibling listing tools.
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% for the single optional 'port' parameter (default 9222), so the schema carries the semantics. The description adds nothing about ports or connection behavior; baseline 3 is appropriate.
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 and resource ('List EVERY open page in the browser') and emphasizes the unfiltered, complete scope ('full inventory from raw CDP'). An agent understands the operation, though it never distinguishes itself from siblings like cdp_targets or cdp_launched, which also enumerate browser targets.
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?
No when-to-use guidance or alternatives are given. The 'EVERY open page' phrasing hints at an unfiltered listing, but nothing tells the agent when to prefer this over cdp_targets or cdp_launched.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.