Lists all open tabs in the collaborative browser with their index, title, URL, and focus status, enabling you to verify which page matches a given tab number.
列出协作浏览器当前所有标签页：序号（0 起，从左到右）、标题、网址、是否聚焦。用户说"看第N个标签页"时，先调用此工具确认序号对应哪一页。
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It implies a read-only operation by saying 'list', but does not explicitly state that it has no side effects or does not modify state. However, the wording strongly suggests it.
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 concise and free of unnecessary words. It efficiently conveys the purpose and the usage hint in two sentences.
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 no parameters and no output schema, the description sufficiently describes what the tool returns (index, title, URL, focus) and provides contextual guidance for when to use it, making it complete for an agent.
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 tool has no parameters, so a baseline score of 4 is applied. The description does not need to explain parameters, and it correctly omits them.
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 states the tool lists all tabs in the collaborative browser, specifying the fields (index, title, URL, focus status). It distinguishes from sibling tools like switch, read, and click by focusing on listing.
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?
It explicitly provides a usage scenario: when the user asks to 'see the Nth tab', call this tool first to confirm the index. This gives clear guidance on when to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.