sleeper_newtab

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. It discloses only 'via extension API', which is implementation trivia, and says nothing about tab focus/activation, whether the tab must be cleaned up later, or what is returned. For a state-creating tool this is a significant gap.

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 short, front-loaded sentence with no filler. Brevity is appropriate, though the terseness contributes to the missing guidance rather than serving it.

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, and one of two parameters undocumented, the description leaves key questions unanswered: does the new tab become active, does it return a tab handle, and how does it relate to sleeper_goto/sleeper_tabs. Inadequate for a tool that mutates browser state.

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 coverage is only 50%: url is completely undocumented in both schema and description, and the description adds no format hints (absolute URL? about: pages allowed?). The profile parameter's meaning comes entirely from the schema's reference to sleeper_sessions, not from the description.

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 clear verb+resource: opening a new tab. It is distinguishable from most siblings in intent, but it never differentiates itself from sleeper_goto (navigate an existing tab) or sleeper_tabs (list tabs), which are the closest alternatives an agent would weigh.

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. The agent is not told whether to use this versus sleeper_goto when it wants a page loaded, nor whether the new tab becomes the active target for subsequent calls.

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