browser_batch

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

With no annotations and no behavioral disclosure, the description fails to inform the agent about side effects, error handling, execution order, return values, or whether it requires a browser context. The 'bail' parameter hints at stopping on error, but this is not explained in the description.

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?

The description is extremely concise with no fluff, but it is under-specified. It provides only a bare phrase, which feels more like a label than a structured description, lacking essential details that an agent needs.

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 tool that executes multiple commands, the description is severely incomplete. There is no information on command format, execution semantics, error behavior, or relationship to sibling tools, making it nearly impossible for an agent to invoke it correctly.

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?

The input schema covers 100% of parameters, and the description adds no additional meaning beyond what the schema already provides. Since schema coverage is high, the baseline score of 3 applies.

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 clearly states that the tool executes multiple commands, specifying a verb ('execute') and a resource ('multiple commands'). However, it does not distinguish itself from sibling tools like browser_eval or browser_click, which also execute actions, so it relies on the term 'multiple' to imply batching.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., an active browser session), scenarios fitting batch execution, or why one would choose it over individual command tools.

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