Batch

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

Annotations already declare it destructive, non-idempotent and open-world, so the bar is lower, yet the description still adds real behavior: execution stops at the first failure unless continue_on_error is set, and a 60000-character cumulative cap causes early termination with a truncated report. It does not cover ordering hazards or whether a partially executed batch can be resumed, keeping it short of a 5.

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?

Three sentences, all load-bearing, with the core definition front-loaded and the failure/truncation caveats following. It is dense without being padded, though the opening could name itself as a sequencer more tightly.

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 nested, write-capable orchestrator with no output schema, the description supplies the essentials an agent needs: shared tab state, fail-fast default, and the truncation behavior of the returned results. A little more on what the truncated response contains would make it complete.

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 100%, so steps, args, tab_id and continue_on_error are already documented; the description only restates continue_on_error's stop/keep-going semantics. The mention of max_chars is arguably a hint about step arguments rather than this tool's own parameters, so it adds limited if any new meaning. Baseline 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?

States a specific verb and resource ('Run several tools in order in one call') and immediately frames itself as an orchestrator that threads one tab through steps, which clearly separates it from the single-action siblings like click, fill, or type. An agent can tell what it is without opening the schema.

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 an explicit use case with a concrete sequence ('fill, fill, click, wait') and the goal ('cut round trips'), plus a routing rule for read-heavy work ('split a read-heavy sequence across calls'). It lacks an explicit statement of when NOT to batch (e.g., for a single step), but the context is clear.

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