batch_extract_web_content

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

No annotations are provided, so the description carries the full burden, and it discharges much of it: failures are isolated per URL ('a single failure does not abort the batch'), results carry an 'error' field, and empty/incomplete batches still return a valid object. It omits auth/credential requirements, rate limits, and timeout behavior, which keeps it short of a 5.

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?

Front-loaded one-line summary followed by labelled 'What it does / How to use / Returns' sections; every bullet adds operational value. The section headings cost a little space but the content is dense and non-repetitive, so it stays efficient.

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?

With no output schema AND no annotations, the description must cover both behavior and returns, and it does explain the return shape (per-URL markdown/tokens/error plus aggregate totals). It is complete enough to call correctly, though it leaves prerequisite/auth and rate-limit concerns unstated.

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%, so the baseline is 3, but the description adds cross-parameter semantics the schema cannot express: mode/css_selector/headers/cookies/proxy apply to every URL in the array, concurrency (1-10) caps parallel workers with advice to keep it modest, and each URL is independent. That is real meaning beyond the per-parameter docs.

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?

States a specific verb+resource+scope: 'Batch extract token-optimized Markdown from multiple website URLs concurrently, with aggregate token statistics.' It explicitly relates itself to the sibling extract_web_content as the same pipeline applied to an array, so an agent can tell the batch tool from the single-URL tool without opening a schema.

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?

Gives clear context: 'Use when you need many pages at once — docs, a list of product pages, a set of sources to compare,' and explains how global options (mode, css_selector, headers/cookies/proxy) apply across all URLs, plus concurrency guidance. It does not state when NOT to use it (e.g., 'for a single URL use extract_web_content'), so routing is implied rather than explicit.

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