List browser targets

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description does not need to restate safety. It adds the notion of 'reconciliation state,' which is not present in the title or annotations, but it never defines what reconciliation state means or how it is represented in the response. This is a moderate gap for a read-only listing tool.

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 concise sentence with a clear subject-verb-object structure and no filler. Every word earns its place, and the most important information ('List controlled browser pages') 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 parameterless tool with strong annotations, the description is mostly sufficient, but 'reconciliation state' is an unexplained domain-specific term that likely matters to the agent. There is no output schema and no hint about the response format, so the description leaves a gap around what the listing actually contains and why reconciliation state matters.

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 has zero parameters, so there is nothing for the description to explain beyond what the schema already conveys. The baseline for 0-parameter tools is 4, and the description does not introduce any parameter-related confusion.

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 clear verb ('List') and a specific resource ('controlled browser pages') plus a distinctive output concept ('reconciliation state'). It is clear enough to separate this from acting tools like act, close_target, or open_url, but it does not explicitly differentiate itself from observation-oriented siblings such as observe or capture.

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?

There is no guidance on when to call this tool versus alternatives like observe, capabilities, or verify. The listing behavior is implied by the verb, but the description never states prerequisites, exclusions, or a preferred scenario such as 'use this before selecting a target to close or interact with.'

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