sleeper_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. 'List connected stable browser installation IDs' honestly conveys this is a read-only enumeration of available browsers, but it omits return format, whether a profile filter narrows results, and any environment requirements.

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 no filler, and the key resource is placed early. It is efficient, though slightly terse enough that 'for routing' reads as an afterthought rather than useful context.

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 simple one-parameter discovery tool with no output schema, the description names what is returned (installation IDs) but does not explain the result shape an agent needs to route to subsequent calls. Adequate but with a clear gap given the absence of an output schema.

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 the single 'profile' parameter is already documented in the schema, including the condition that it is optional with one connected browser. The description adds nothing beyond what the schema provides, so baseline 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 (connected stable browser installation IDs), which clearly distinguishes it from the action-oriented siblings like sleeper_goto and sleeper_click. The trailing 'for routing' is slightly vague but the core purpose is unambiguous.

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 explicit guidance on when to call this tool versus alternatives. 'For routing' hints that the returned IDs feed other calls, but it never states the trigger condition or that this is the discovery step before tools requiring a profile. An agent must infer usage from the param note alone.

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