sleeper_snapshot

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing. It does not state whether the call is a pure read (implied but unconfirmed), whether it covers only the top frame or all frames, whether hidden elements are included, or what the returned structure looks like.

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?

At five words it is maximally terse and front-loaded with the element categories, with zero filler. However, the brevity here reads as under-specification rather than efficient economy, since key scoping information is simply absent.

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?

There is no output schema, so the description is the only place the return shape could be explained, and it only hints at four element categories. Combined with a crowded sibling set and no annotations, an agent lacks enough context to pick this tool confidently or predict its output.

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 (tab, profile) are documented in the schema, so the baseline of 3 applies. The description adds nothing about how tab selection or the optional profile interacts with the snapshot behavior.

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 fragment 'Headings/inputs/buttons/links summary' names the resource categories it covers, so an agent can guess it returns a page-level digest of interactive and structural elements. But it is a noun phrase with no verb and no scope statement, and it does not differentiate itself from close siblings like sleeper_read, sleeper_read_all, or sleeper_extract.

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 when-to-use guidance at all: no condition selecting it over sleeper_read_all, sleeper_extract, or sleeper_state, and no note on when a snapshot is preferable to a targeted query. The agent must infer the use case entirely from the name.

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