crawl_website

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

The description adds behavioral context beyond the annotations: it explains that the tool follows links up to a specified depth and that scraper_config can reference saved settings or inline options. This is useful because it reveals how the crawl operates, while readOnlyHint and openWorldHint already cover the safety profile.

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 three sentences with no filler. It front-loads the core purpose, then adds the key behavior around depth and scraper_config. Every sentence 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?

The core crawl behavior, depth, and scraper_config usage are covered, but the tool has a nested object, six parameters, and no output schema. The description does not explain return format, async behavior, or how max_urls affects the crawl. This is adequate but has clear gaps for a tool of this 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 coverage is about 50%, and the description partially compensates by clarifying that depth controls how far links are followed and that scraper_config accepts config_id or full options. However, max_urls and async_mode receive no semantic explanation in either the schema or the description.

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 a specific verb and resource: 'Crawl a website to discover and scrape multiple pages.' This distinguishes the tool from siblings like scrape_url, which targets a single page, and map_website, which is about mapping links rather than scraping content.

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 implies this tool is for multi-page crawling and scraping via 'discover and scrape multiple pages' and 'follows links up to specified depth,' but it never gives explicit when-to-use or when-not-to-use guidance, nor does it name alternative tools like scrape_url or map_website.

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