batch_scrape

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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions parallel execution, but omits important details like error handling, rate limits, resource usage, result ordering, or failure behavior.

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 a single concise sentence with no wasted words, and the key point is front-loaded. However, it is too terse to be fully useful, though conciseness itself is not a flaw.

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?

Despite having an output schema, the description is incomplete for a tool with 4 parameters and no annotations. It lacks critical usage context such as how to set formats, worker counts, timeout profiles, and any operational cautions for parallel scraping.

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 0%, and the description does not compensate by explaining any of the four parameters (urls, format, workers, timeout_profile). It only implicitly references 'urls' without providing syntax, defaults, or meaning for the others.

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 'Scrape multiple URLs in parallel' uses a specific verb ('scrape') and resource ('multiple URLs'), clearly distinguishing it from sibling tools like scrape_url. The phrase 'in parallel' adds a distinctive characteristic.

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 such as scrape_url or crawl_site. It does not state exclusions, prerequisites, or typical use cases beyond the basic function.

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