zapfetch_crawl

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

Despite no annotations, the description clearly states it is long-running and returns a job_id for async polling. It also advises considering user consent for large sites, which covers important behavioral aspects.

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?

Concise, with key information front-loaded. Every sentence adds value: defines the tool, specifies async nature, warns about runtime, and gives alternatives. No fluff.

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 tool's complexity (crawling, async, multiple parameters), the description covers purpose, usage boundaries, behavioral notes, and alternatives. No output schema needed since it returns a job_id; the polling tool likely handles that.

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 baseline is 3. The description does not repeat param details but adds context by explaining the overall behavior (async) and when to use. Since all parameters are well-documented in schema, the description adds value indirectly.

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 it crawls a website and extracts content from multiple pages, using specific verbs ('crawl', 'extract'). It distinguishes from siblings: 'For a single page, use zapfetch_scrape. For URL discovery only (no content), use zapfetch_map.'

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?

Explicitly tells when to use (multi-page content gathering) and when not to (single page -> zapfetch_scrape, URL discovery -> zapfetch_map). Also warns about long-running nature and suggests asking user before invoking on large sites.

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