browser_chain

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

With no annotations, description discloses automatic error checking, stop-on-error behavior, and enforceValidation mode forcing error checks. Does not mention side effects on browser state or return value details.

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?

Two concise sentences in Chinese covering main features without redundancy. Front-loaded with primary function.

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; description mentions returning failed step but does not specify full output structure. Lacks clarity on chain execution context and state persistence.

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%; the description does not add parameter-specific details beyond the schema's descriptions. Purpose of parameters is clear from schema alone.

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 it chains multiple browser operations with automatic error checking, distinguishing it from individual browser action tools. It specifies chaining, error checking after each step, and forced validation mode.

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?

No explicit guidance on when to use this tool versus alternatives. Implies use for sequences needing error checking, but lacks when-not or alternative suggestions.

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