sleeper_focus

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

No annotations are provided, so the description carries the entire burden of behavioral disclosure, and it discloses nothing. It does not say whether focusing scrolls the element into view, whether it mutates page state, whether it requires the element to already exist or be visible, or what the call returns.

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?

Two words is terse but not concise in the useful sense: the brevity comes from under-specification rather than efficiency. There is no front-loaded explanation because there is no explanation.

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 annotations, no output schema, three parameters at 33% coverage, and a required selector that is undocumented, the description is fully inadequate for an agent to call this tool correctly or predict its effect.

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 only 33% (only profile is documented; tab and the required selector have none). The description adds no meaning for any of the three parameters, leaving the required selector and tab semantically undefined in both places.

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?

"Focus element" is essentially a two-word restatement of the tool name sleeper_focus with its object tacked on. It gives no scope (single element? page focus? tab focus?) and never distinguishes itself from the many sibling interaction tools (click, hover, dblclick, check). An agent cannot tell from this what focusing actually accomplishes.

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, when-not-to-use, or alternative guidance of any kind. Nothing tells the agent whether to reach for sleeper_focus instead of sleeper_click or sleeper_hover, which are adjacent sibling actions on elements.

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