sleeper_state

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

No annotations are provided, so the description carries the full burden. 'Get' implies a non-mutating read, and the parenthetical discloses the shape of the returned state, but there is no statement about permissions, whether it waits for the page to settle, or what happens if no profile is connected.

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?

One front-loaded sentence with the returned fields in parentheses; every token earns its place and there is no 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?

With no output schema, the description must convey what comes back, and it does at a coarse level (url, title, focus, visibility). For a one-optional-parameter read tool with no annotations this is nearly sufficient, though it says nothing about error or disconnected-profile behavior.

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 the single optional 'profile' parameter is fully documented in the schema (Browser ID from sleeper_sessions). The description's mention of the 'selected Sleeper profile' loosely echoes that parameter but adds no syntax or default-behavior detail beyond the schema, 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 ('Get') and resource ('page state') and enumerates the returned fields (url, title, focus, visibility), which is more informative than the bare name. It does not, however, distinguish itself from close siblings like sleeper_snapshot, sleeper_tabs, or sleeper_read, so an agent still has to guess which state-reading tool applies.

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 no when-to-use guidance and no exclusions. With siblings such as sleeper_snapshot, sleeper_tabs, sleeper_read, and sleeper_find all plausibly overlapping, the agent receives no routing signal for picking this one.

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