sleeper_batch

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

No annotations, so the description carries the full burden. It usefully discloses that execution is ordered and halts on the first failure by default, but omits what a failure returns, whether partial results are reported, the 50-action cap, and any tab/profile 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 tight sentence with the core behavior front-loaded and zero filler; appropriately sized, though perhaps too terse given the tool's complexity.

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 complex batch tool with a nested action array, no annotations, and no output schema, the description is far too sparse. It never explains what cmd values are valid or how results/errors are surfaced, leaving essential invocation knowledge missing.

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 33%: profile is documented in the schema and stop_on_error's default is echoed by the description, but the critical 'cmd' field and the nested 'tab'/'args' semantics are explained nowhere, so the description fails to compensate for the coverage gap.

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 and resource: 'Run ordered browser actions in one request.' This clearly frames it as a batch executor over the many single-action siblings, though it never explicitly says it batches those sibling commands.

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?

Implies usage via 'in one request' (batch multiple actions for efficiency), but gives no explicit when-to-use vs the individual action tools, no prerequisites, and no exclusions.

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