list_pages

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

Annotations already declare readOnlyHint=true, and the description's 'Get a list' aligns with a read operation. It adds scope by specifying 'pages open in the browser,' but does not elaborate on return format, ordering, or whether it includes all tabs/windows. This adds moderate context above the annotation.

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, direct sentence with no filler. Front-loaded with the action and target.

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 is simple with no params and a read-only hint. The description conveys the core purpose. However, without an output schema, it does not state what the list contains (e.g., page titles, URLs), which would be useful for an agent to decide whether to call it. Still, for a basic list operation, it's adequate.

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 zero parameters, and the schema shows 100% coverage (empty object). The description does not need to explain parameters, and the baseline for 0 params is 4. No additional parameter info is required.

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?

Description uses a specific verb 'Get a list' and clearly identifies the resource 'pages open in the browser.' It distinguishes from sibling tools like 'select_page' and 'navigate_page' by focusing on enumeration rather than selection or navigation.

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 when the agent needs to discover open browser pages. However, it does not explicitly mention when to prefer this over alternatives like 'select_page' or 'navigate_page,' though the difference is inferable. Context is clear, but exclusions are not stated.

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