list_pages

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

With no annotations, the description carries the behavioral disclosure burden. It explains what 'connected' means and how a page becomes eligible, which is meaningful behavioral context. It does not describe exact return shape or ordering, but this is a simple read-only listing operation.

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 long. The first sentence states the core purpose directly, and the second adds essential lifecycle context. No filler or redundant wording exists.

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 simple no-parameter listing tool with no output schema, the description provides enough information for an agent to invoke it correctly and interpret what will be returned. It explains when pages connect, which is the main operational nuance. A return-value hint would be marginally useful but is not essential here.

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 confirms this. Per the zero-parameter baseline, the description does not need to add parameter information, and the score is set to 4.

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 states a specific verb-resource pair: 'List browser pages currently connected to the live bridge.' This clearly distinguishes it from sibling tools that list captures or manage files, and it immediately communicates what operation is performed.

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 gives clear context for when pages appear in the list by explaining the connection lifecycle (after instrumentation or self-initialization). It does not explicitly name alternatives or exclusions, but for a zero-parameter listing tool this is sufficient guidance.

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