stealth_scrape

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

No annotations provided, but the description explains it uses StealthyFetcher with Patchright, is slower than crawl_url, requires browser binaries setup, and can handle Cloudflare and JS rendering. However, it does not disclose error handling if binaries are missing or any rate limits.

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?

Well-structured with a clear opening, setup note, usage list, and examples. Every sentence adds value, no redundancy.

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?

Covers main purpose, context, and usage scenarios, but omits details on some parameters (reasoning, max_chars, headless, country) and potential error states. Output schema exists, so return values are not required.

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%, yet description explains wait_selector and solve_cloudflare implicitly via examples and text. However, it does not document reasoning, max_chars, headless, or country, leaving significant gaps beyond what the schema provides.

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 scrapes a URL using a stealth browser to bypass anti-bot protections, and distinguishes from sibling tool crawl_url by noting it is slower but works on protected sites.

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?

Provides explicit when-to-use conditions (e.g., crawl_url returns Cloudflare challenge, site blocks automated requests, JS rendering needed) and includes two concrete examples, aiding the agent in correct selection.

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