Run browser action sequence

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description does not need to repeat those. It adds the default stop-on-failure behavior, which is not in the annotations, and implies ordered execution. However, it does not disclose other traits like side effects on the browser state or that the sequence may be interrupted. The added context is modest, earning a middle score.

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 a single, efficient sentence that front-loads the core purpose and a key default behavior. It contains no wasted words and is appropriately brief for a tool whose schema carries the heavy detail. Every clause earns its place.

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?

This is a complex batch tool (up to 100 actions, many subfields) with no output schema, yet the description is minimal. It does not explain when to prefer it over sibling tools, how actions relate to browser_capabilities, or what the stopOnError parameter controls in practice. While the schema provides technical detail, the description fails to provide the usage context an agent needs to decide when to invoke this tool, leaving significant gaps.

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 description coverage is 0% – the description provides no information about the two parameters (actions, stopOnError) or their meaning. The schema itself does contain detailed sub-field descriptions, but the description does not compensate for the low coverage. An agent would have to rely entirely on the schema, and the description adds no semantic help for choosing or structuring the 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 action ('execute an ordered sequence') and a clear resource (one selected browser), with a notable behavioral detail (stopping on failure by default). It clearly distinguishes from the sibling browser_action which likely runs a single action, though it does not name that sibling explicitly. This is clear but not maximally explicit about alternative tools.

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?

The description gives no explicit guidance on when to use this tool versus alternatives. It implies use for multiple actions but does not state 'use this instead of browser_action for sequences' or provide exclusions. The 'stopping on failure' default is a behavior, not a usage condition. An agent must infer from the name and schema that this is for batching.

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