scrape_url

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

No annotations provided, so the description carries full burden. It discloses bypassing mechanisms, output format, and authorization requirements. However, it does not describe error behavior, rate limits, handling of invalid URLs, or the exact behavior of json_output parameter (which may return structured JSON despite the description stating 'Returns as clean Markdown').

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 focused sentences convey purpose, capabilities, requirements, and constraints without any wasted words. The description is efficiently front-loaded with the key functionality.

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 moderate complexity (2 params, no output schema), the description covers the essential aspects: what it does, prerequisites, authorization, and output format. Minor gaps include error handling, rate limits, and the exact nature of JSON output, but overall it provides sufficient context for safe and effective use.

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 50% (only json_output has a description). The description adds context for the url parameter (target URL) and implies json_output changes output from Markdown to JSON. However, details like URL format, encoding, max length, and the exact structure of JSON output are missing.

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 the verb (fetch/scrape), the resource (any public URL), and the specific capabilities (bypassing Cloudflare, CAPTCHA, bot-protection) with a clear output (clean Markdown). It naturally distinguishes from sibling search tools which focus on querying databases or services.

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 explicitly names required environment variables (BRIGHTDATA_API_KEY, BRIGHTDATA_UNLOCKER_ZONE) and provides authorization guidance ('your own assets or authorized target'). While it doesn't explicitly contrast with alternatives, the tool's unique purpose among siblings makes the usage context clear.

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