Run reproduction steps

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

Goes well beyond the annotations: annotations only say readOnly=false, destructive=false, openWorld=true, whereas the description discloses the allowlist mechanism, the JavaScript prohibition, and the blocking policy for state-changing HTTP and destructive-looking controls. That is exactly the kind of policy context an agent needs before submitting steps.

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, no filler, and the core behavior is front-loaded before the constraint sentences. Every sentence carries distinct information (capability, sandboxing limit, safety blocking).

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 an output schema exists and annotations cover the read/write profile, the description covers the key behavioral risk surface. Minor gaps: it does not mention that execution stops at the first failure by default (continueOnFailure) nor the 50-step cap, both of which affect how an agent should build a step list.

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% and the discriminated-union step schema fully enumerates the actions and their shapes. Naming the action list in prose is mildly reinforcing but adds no semantics the schema does not already carry; 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 ('Executes an ordered list of allowlisted browser actions') plus the side effect it produces ('records the outcome of every step'). The enumerated action set (navigate, click, fill, select, reload, waitFor, screenshot) makes it immediately distinguishable from the investigation/evidence/report siblings.

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?

Makes the operating envelope explicit — no arbitrary JavaScript, state-changing requests and destructive clicks are blocked unless operator-enabled — which tells the agent when this tool will and will not work. It does not explicitly route against siblings (e.g., 'use after start_investigation, before generate_bug_report'), leaving that to the investigationId param description.

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