list_browser_sessions

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose two useful traits beyond the schema: results are ordered newest first and paging is cursor-based. It omits auth/permission requirements, whether the operation is read-only (only implied by 'List'), rate limits, and what the returned session records contain.

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?

A single front-loaded sentence with zero filler: the resource is named first, then ordering and pagination. Every clause carries information an agent can act on.

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-required-parameter read tool this covers the essentials, but with no annotations and no output schema the description could have stated the read-only nature and that responses include session records plus a nextCursor for continued paging. The pagination hint is present but the return shape is left to inference.

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 100%, so all three parameters (limit, cursor, status) are already documented in the schema, including the enum values and the nextCursor reference. The description adds only the generic notion of cursor pagination and does not enrich parameter meaning beyond the schema, so the baseline of 3 applies.

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?

States a specific verb (List) and resource (Cloud Browser session history) with added scope detail: ordering ('newest first') and pagination mode ('cursor pagination'). The plural resource and 'history' framing distinguish it from the singular sibling get_browser_session, though no sibling is named explicitly.

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?

Usage is only implied by the phrase 'session history' — an agent can infer this is for enumerating past sessions, and the ordering/pagination hints suggest it is the paging entry point. There is no explicit when-to-use, when-not, or reference to alternatives such as get_browser_session for a single record, nor any note on using the status filter.

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