scrape_batch

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: batch processing of multiple URLs (implied by 'multiple webpages'), advanced content extraction, output in MarkDown, and ability to bypass bot detection/CAPTCHA. However, it lacks details on rate limits, error handling, authentication needs, or what 'advanced options' entail, leaving gaps for a mutation-like operation.

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 with two sentences that efficiently convey core functionality. The first sentence covers purpose and output, while the second adds behavioral context. No wasted words, though it could be more structured by explicitly separating features from limitations.

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 no annotations, no output schema, and a single parameter with full schema coverage, the description is moderately complete. It covers what the tool does and key capabilities (bypassing bot detection), but lacks details on return values, error cases, or performance constraints, which are important for a web scraping tool with potential complexity.

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%, with the schema fully documenting the 'urls' parameter (array of URIs, min 1, max 10). The description adds no parameter-specific semantics beyond implying batch processing through 'multiple webpages URLs.' Since schema coverage is high, baseline 3 is appropriate as the description doesn't significantly enhance parameter understanding.

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's purpose: 'Scrape multiple webpages URLs with advanced options for content extraction and get back the results in MarkDown language.' It specifies the verb (scrape), resource (webpages), and output format (MarkDown). However, it doesn't explicitly differentiate from sibling tools like scrape_as_markdown, which might be for single URLs, so it misses full sibling distinction.

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 provides no guidance on when to use this tool versus alternatives. It mentions 'advanced options for content extraction' and ability to 'unlock any webpage even if it uses bot detection or CAPTCHA,' but doesn't specify when to choose this over scrape_as_markdown or search_engine tools. No explicit alternatives or exclusions are provided.

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