browser_list_pages

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

No annotations are provided, so the description carries the full burden. It states the scope (current task) but does not disclose return format, whether it affects browser state, or any side effects. The description is essentially a restatement of purpose without additional behavioral context.

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, clear sentence that front-loads the action. It contains no unnecessary words and is immediately understandable.

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?

The tool has no output schema, and the description does not explain what information is returned for each tab (e.g., id, title, URL). It also does not clarify the relationship between task_id and the current task. Lacking these details, an agent might not know what to expect from the tool.

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 schema has one parameter (task_id) with no description (0% coverage). The description mentions 'current task' which hints at the parameter's role, but it does not explain how task_id is used, accepted values, or behavior for different inputs. The description does not fully compensate for the lack of schema documentation.

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 open tabs for the current task, using a specific verb ('列出') and a specific resource ('标签页'). It distinguishes from sibling tools like browser_list_sessions or browser_tasks by focusing on tabs/pages rather than sessions or tasks.

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 when to use this tool (to see open tabs for a task) but provides no explicit guidance on alternatives or when not to use it. It does not compare with sibling tools, so usage context is only inferred.

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