Get Crawl / Web Scraper results

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

With no annotations, the description carries the full burden. It discloses that if the job is still running, it returns status, which is important behavioral information. But it doesn't describe what happens on completion beyond 'download the data', nor does it mention error handling, timeouts, or how to interpret status codes. This is adequate but minimal.

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 two concise sentences, front-loaded with the primary action ('Check progress and download data') and omits unnecessary details. Every phrase 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?

Given the simple 2-parameter schema and no output schema, the description covers the basic flow: check progress, download when ready, return status if still running. However, it doesn't explain the structure of the response or data, potential failure modes, or how to identify 'ready'. It's minimally complete but lacks depth for a fully self-contained description.

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 0%, so the description must compensate. It explains that snapshot_id is returned by web_scraper_trigger, adding provenance. However, it says nothing about the 'format' parameter (json, ndjson, jsonl, csv) or its default, leaving users to infer from the schema. The description adds only limited value over the schema.

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 what the tool does: 'Check progress and, when ready, download the data for a snapshot_id'. The verb is specific, and the resource is a snapshot_id tied to web_scraper_trigger, which distinguishes it from sibling tools that scrape specific websites or trigger new scrapes.

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 explicitly says the snapshot_id comes from web_scraper_trigger, implying this tool is used after triggering a job. This provides clear context for when to call it. However, it doesn't state when not to use it or mention alternative result-fetching tools, so it lacks explicit exclusions.

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