browser_chain

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

No annotations are provided, so the description must carry the burden. It discloses error-checking behavior, stop-on-error, and enforce mode details. However, it does not mention side effects on browser state or session persistence, which are important for a chaining tool.

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 concise (two sentences) and front-loads the main purpose. Every sentence adds value, though it could be more structured with bullet points for clarity.

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?

No output schema is provided. The description explains error checking but lacks details about return format or what 'return failed step' means. Given the complexity of chaining and many siblings, more context on output and when to chain vs. step would improve completeness.

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 coverage is 100%, and parameters are well-documented. The description adds minimal value by noting that 'step.type' and 'step.action' are aliases and at least one required, which is already implied by anyOf. No additional semantics beyond schema.

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 the tool chains multiple browser operations with automatic error checking after each step. It distinguishes itself from single-step tools like browser_step and similar chaining tools by specifying error-checking and enforce-validation features.

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 explains the general behavior (error checking, termination on error, enforce mode) but does not explicitly specify when to use this tool over alternatives like browser_flow or browser_step. No guidance on prerequisites or exclusions.

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