List browser pages

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds that it lists pages 'belonging only to the addressed session', which clarifies scope but does not add much beyond annotations. It does not describe return format or pagination, but with annotations covering safety, a 3 is appropriate.

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 two sentences, front-loaded with the purpose, and every word adds value. It is concise and well-structured.

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 one parameter and an output schema exists, so the description need not explain return values. The description covers the purpose and usage context adequately. It could mention that it returns a list of page IDs, but the output schema likely covers that. Given the simplicity and annotations, the description is complete enough.

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 0%, but there is only one parameter (sessionId) with a clear name and type. The description mentions 'addressed session' which implies the sessionId parameter, but does not add detailed semantics beyond what the schema provides. Since the parameter is self-explanatory and the description references it, a 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?

The description clearly states the tool lists pages belonging to a specific session, using the verb 'List' and specifying the resource 'pages' and scope 'session'. It distinguishes from siblings like browser_session_list (which lists sessions) and browser_page_create (which creates pages).

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 provides clear context: it is used to rediscover or inspect all pages in a session, and notes that session creation already returns the initial pageId. It implies when to use this tool (when you need to see all pages in a session) but does not explicitly mention alternatives or when not to use it, though the sibling list makes alternatives apparent.

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