List saved browser states

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

The description discloses a key behavioral trait beyond the annotations: 'state contents and secrets are not returned'. This prevents an agent from assuming that listing states returns full state data. Combined with the readOnlyHint, idempotentHint, and destructiveHint annotations, the tool's behavior is transparent.

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, well-structured sentence. It front-loads the action and resource, then adds the scope and a crucial negative detail without unnecessary words.

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 zero-parameter listing tool with strong annotations and an output schema, the description is complete. It clarifies what is returned (IDs only) and what is not returned (contents/secrets), leaving no major gaps for an agent selecting or invoking the tool.

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 an empty input schema, so there is no parameter semantics to explain. The baseline for no parameters is 4; the description correctly implies no inputs are needed.

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 starts with the specific verb 'List' and identifies the resource as 'logical saved-state IDs', while also clarifying they are 'available for optional restoration when creating a new isolated session'. This clearly distinguishes it from sibling tools like browser_session_list or browser_state_save.

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: this tool is used to enumerate saved-state IDs for optional restoration during isolated session creation. It does not explicitly state when not to use it or name alternatives, but the use case is specific enough to guide an agent effectively.

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