session_pages

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

With no annotations, the description carries the transparency burden. It discloses non-obvious behavior: popups are automatically attached, get a page_id, and are immediately usable by all page_* tools, and it specifies the JSON return shape. It does not explicitly declare read-only status or failure behavior, but 'list' and the return-only description make the operation's nature clear.

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?

Two sentences, no filler. The first sentence labels and scopes the operation; the second adds the key behavioral detail and return format. The most important information is front-loaded.

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?

For a one-parameter list tool with no output schema, the description gives the essential output format and a crucial behavioral detail (popups are immediately usable). It lacks a small amount of context around session_id provenance and empty/error cases, but overall an agent can call it correctly.

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 input schema exposes only a required session_id string with no description, and schema description coverage is 0%. The tool description never mentions session_id, where to get it, or how it scopes the listed targets, so it fails to compensate for the schema's missing parameter 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?

Description uses a specific verb and resource: it lists every browser target in the session, including user-opened pages and site-opened popups. It explicitly distinguishes itself from the page_* siblings by being the enumeration tool that returns page_id for all targets rather than operating on a single page.

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?

Clear context is provided: use it whenever you need a complete inventory of pages and popups, especially OAuth/payment flows. It implies this should precede use of page_* tools because popups are auto-attached with usable page_id, but it does not explicitly name alternatives or give when-not conditions.

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