Trigger a Crawl / Web Scraper job

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

With no annotations, the description carries the transparency burden. It discloses the asynchronous trigger nature, the snapshot_id return contract, and the dataset_id prerequisite/fallback. It does not mention costs, rate limits, or failure modes, but covers the essential behavioral contract for a trigger tool.

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 tightly written sentences front-load the core verb and resource, then add the return/polling contract and the dataset_id requirement. No filler or repetition of schema details.

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?

The tool is a simple async trigger with a required urls array and several optional parameters, and the description explains the most important missing piece: what the caller receives and how to continue via web_scraper_get_results. It could add guidance for extra_inputs or when to choose a specialized web_data_* tool, but the schema plus description is largely sufficient.

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 coverage is ~80%, so the baseline is 3. The description adds meaning beyond the schema for dataset_id (argument vs BRIGHTDATA_DATASET_ID fallback) and the overall return contract, but does not elaborate on extra_inputs, include_errors, or custom_output_fields beyond what the schema already states.

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 opens with 'Trigger a Bright Data dataset (Web Scraper / Crawl API) collection over one or more URLs,' which names a specific action and resource. It immediately distinguishes itself from the sibling web_scraper_get_results by stating it returns a snapshot_id to poll with that tool.

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?

It provides clear usage context: the tool triggers a collection and returns a snapshot_id to poll with web_scraper_get_results, plus a note on dataset_id via argument or BRIGHTDATA_DATASET_ID. It does not spell out when to prefer this over the many web_data_* siblings, so it stops short of full exclusion guidance.

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