list_sessions

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

With no annotations, the description carries the burden of disclosing behavior. 'List... sessions' implies a read-only operation, and 'whether a login window is open' adds useful behavioral context. But it does not explicitly confirm lack of side effects or describe any state changes, which matters given no annotation safety hints.

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 sentence that starts with the verb 'List' and communicates the core behavior immediately. There is no filler or redundant information.

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?

A tool with zero parameters and an output schema does not need extensive description. The main gap is the lack of explicit guidance on when to use this vs. sibling tools, but the simple nature and existing output schema make the description sufficiently complete for correct invocation.

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, so parameter documentation is unnecessary. The description adds no parameter detail, but none is needed; the baseline of 4 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?

The description states a specific verb and resource: 'List saved website sessions' and adds a distinguishing detail, 'whether a login window is open.' It clearly differentiates this read-only listing tool from the action-oriented siblings like sign_in, revoke, and browse.

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 implies its usage: use it to view saved sessions and login-window state. However, it does not explicitly say when to choose this tool over siblings, mention prerequisites, or give context such as checking sessions before signing in.

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