browser_tabsLists all open browser tabs and in-app WebView pages on Android devices, including attached sessions, so you can inspect active web content.
Every open page across the on-device browser and in-app WebViews, plus attached sessions.
| Name | Required | Description | Default |
|---|---|---|---|
| device | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only describes scope, not whether this is a read-only listing, whether it opens any sessions, what permissions are needed, or what happens with attached sessions. It adds minimal context about coverage but no real behavioral transparency.
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 one short, front-loaded sentence with no filler, and the scope detail is useful. However, it sacrifices necessary verb and parameter information for brevity, reading more like a category label than a complete tool description.
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?
With no annotations, a 0%-covered parameter, and a one-line noun-phrase description, the definition is insufficient for an agent to safely invoke the tool. The presence of an output schema reduces the need to describe return values, but the missing action and device semantics remain significant gaps.
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 single optional 'device' parameter has 0% schema description coverage, and the description never mentions it. The agent cannot determine what device selects, whether null means the current device or all devices, or how the parameter interacts with 'attached sessions'.
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 identifies the resource (open pages in the on-device browser and WebViews, plus attached sessions) and helps distinguish it from sibling browser tools, but it is a noun phrase rather than an explicit action. It never states that the tool lists or returns tabs, so an agent must infer the behavior from the name 'browser_tabs'.
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?
There is no guidance on when to use this tool versus alternatives like browser_close, browser_read, get_ui_tree, or perceive_screen. No context is given for when querying attached sessions is appropriate or how this relates to the optional device parameter.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.