Perform sequential page actions

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

With no annotations, the description carries the full burden. It discloses fail-fast behavior, DOCUMENT_HIDDEN failure for click/type/keypress unless allowHidden=true, and documentId revalidation before every step and after observation. This is substantive behavioral context beyond the schema, though it does not cover scroll-specific behavior or return values.

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 with zero redundancy. The main purpose is front-loaded, and each subsequent sentence adds a critical behavioral constraint. It is compact and well-structured.

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?

The description covers the core behavior (batch execution, fail-fast, hidden handling) but does not mention the 'after' observation feature or other parameters like tabId/sessionTabId. However, those are fully described in the schema, and the description provides enough high-level context for an agent to understand the tool's primary function and constraints.

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 baseline is 3. The description adds meaning beyond the schema by explaining documentId revalidation (steps cannot override it) and the allowHidden exception for hidden documents. These nuances are not present in the parameter descriptions themselves.

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 and resource: 'Run up to 10 sequential page actions in one document target.' It clearly distinguishes this from sibling tools like click/type/scroll by emphasizing batch execution and the single-document constraint. The mention of fail-fast and DOCUMENT_HIDDEN behavior further clarifies its role.

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 implies this is for batching multiple actions, but it does not explicitly contrast with single-action siblings (click, type, scroll) or state when to prefer this tool over them. The documentId revalidation and hidden-document notes give some context, but no explicit 'use this for multiple actions; use click for a single action' guidance.

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