browser_batch

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

No annotations are provided, so the description must carry behavior. It discloses the tab targeting behavior and the list of available actions, and notes parallelism limits. However, it does not describe return format, error handling, ordering guarantees, or auth/rate constraints.

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-loaded purpose sentence, followed by structured action list and example. Slightly verbose due to listing every action, but each part is useful. No filler.

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?

Given no annotations and no output schema, the description covers the core invocation pattern and action enumeration, which is the most important missing schema information. It still omits return values, error semantics, and detailed parameter contracts for individual actions.

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 says commands is an array of objects. The description compensates substantially by explaining the command dict shape (action + parameters) and giving an example, plus the tabId convention. This is better than 0% coverage but not exhaustive for all action parameters.

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 description states a specific verb (run multiple commands), resource (commands in a single request), and benefit (for speed). It clearly distinguishes itself from the many single-action siblings by being the batch runner.

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?

It provides clear context: use for speed and targeting specific tabs via tabId. It explicitly points to browser_parallel for true concurrency. It does not state exclusions or when not to use batching beyond that, but the routing to an alternative is strong.

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