fetch_batch

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

Discloses parallel browser instances, isolation, auto-detected stabilization, and same-order results, but lacks depth on resource usage, rate limiting, or meaning of 'stabilization'. With no annotations, more detail would benefit agent decision-making.

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 concise sentences front-load critical purpose and behavior, with no redundant information. Every sentence earns its place.

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 and description does not detail return structure beyond order preservation. For a tool with 4 parameters and no output schema, more contextual information on results 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 covers 100% of parameters with descriptions. Description adds context about isolation for urls and auto-detection for human_mode, but this is marginal beyond schema. Baseline score appropriate.

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 fetches multiple URLs in parallel using real Chrome browsers with isolation and auto-stabilization, distinguishing it from the sibling tool 'fetch' which likely handles single URLs.

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 usage for multiple URLs needing parallel fetching and isolation, but does not explicitly state when to use versus alternatives, nor provide exclusions or prerequisites.

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