browser_parallel

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

With no annotations, the description carries the full burden and does well: it discloses the concurrency model (inner serial, outer concurrent), the race-condition hazard over the active tab, and the return shape. It omits failure semantics, e.g. whether one failing sequence aborts the batch, which is the main remaining 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?

Front-loads the core semantics before the tabId constraint, then the return value, then the argument detail. The example is worth its length, though the Args block is slightly verbose for a single parameter.

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?

No output schema exists, and the description fills that gap by describing the return value as one result list per input sequence. Combined with the concurrency and tabId guidance it is largely complete; only error/partial-failure behavior is unaddressed.

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 0% and the schema only shows an untyped array-of-arrays, so the description must compensate — and it does, defining each command as a dict of action plus parameters, matching browser_batch, and providing a two-tab worked example. This fully specifies the single parameter.

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 command sequences in parallel') and immediately scopes it with 'typically one sequence per tab.' It is distinguishable from the serial sibling browser_batch, which it explicitly references for command shape.

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?

Gives clear context for use (concurrent sequences, one per tab) and a concrete constraint for correctness: tab-aware commands MUST include tabId to avoid race conditions. It stops short of an explicit 'use browser_batch instead when...' exclusion, so it is strong but not fully routing.

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