browser_batch

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

No annotations provided; description mentions max 20 steps and operation types, but fails to disclose execution order, error handling, or side effects like navigation from click, leaving significant behavioral gaps.

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 sentences, front-loaded with key idea, but too terse; missing essential behavioral details that could have been included without losing conciseness.

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 complex batch tool with no output schema or annotations, the description lacks critical context about execution guarantees, response format, and failure behavior, leaving it incomplete.

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% (all parameters have descriptions); description adds little beyond repeating parameter concepts (type, selector, text) and the maxSteps default, meeting baseline but not adding value.

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?

Clearly states it batch-executes multiple browser operations, listing operation types and distinguishing from single-operation sibling tools (e.g., browser_click, browser_type).

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?

Implies use when multiple browser operations are needed, but provides no explicit guidance on when not to use or alternatives, leaving context inferred from sibling tool names.

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