List open browser sessions

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

Annotations already cover read-only/idempotent/non-destructive safety, so the bar is lower; the description adds real value by disclosing that sessions stay warm, parked on a page, and keep billing while open, plus the resumable flag concept. It stops short of describing pagination or ordering of results, which keeps it from a 5.

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?

Front-loads the purpose and the resume rationale before naming alternatives; every clause carries instruction. Slightly dense with the billing aside, but nothing is filler.

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?

No output schema exists, so the description usefully enumerates the returned fields (id, status, resumable flag, current url, goal), and it supplies the workflow context needed to act on the result. Nothing an agent needs to call or use the tool is missing.

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% and both parameters (limit, include_closed) are documented there, so the schema does the heavy lifting. The description never references limit or include_closed, adding nothing beyond the schema — the baseline 3 when coverage is high.

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+resource (list open cloud browser sessions) with account scope, and explicitly differentiates itself from siblings by naming writ_browser_use, writ_browser_act and writ_browser_context. An agent can select it vs. those tools without reading any schema.

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?

Gives explicit when-to-use ('when you need a browser, check here first'), the when-not ('rather than calling writ_browser_use again'), and the follow-on action (pass session_id to writ_browser_act / writ_browser_context). The alternative path is fully spelled out.

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