scrape

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

No annotations are provided, so the description carries the full burden. It discloses non-obvious behavior such as Cloudflare bypass, retries, and optional metadata. However, it does not mention error handling, rate limits, authentication, or response behavior on non-200 statuses, leaving meaningful gaps.

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 one tightly written sentence that front-loads the primary action ('Fetch a URL'), then names the key behavioral traits and return type. No filler or redundant content.

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 there are no annotations and no output schema, the description plus schema is adequate but not rich. It covers raw HTML output, Cloudflare bypass, and retries, but it lacks guidance on error behavior, response metadata details, and when to prefer DOM-focused sibling tools.

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 the schema already documents all six parameters. The description adds little beyond 'Cloudflare bypass' and 'optional metadata,' and it does not clarify method, headers, timeout, or retry semantics 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 uses a specific verb and resource: 'Fetch a URL with Cloudflare bypass, retries, and optional metadata. Returns raw HTML.' The phrase 'raw HTML' distinguishes it from sibling tools like scrape-dom or dom, which likely return parsed or extracted DOM 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 usage for fetching raw HTML and bypassing Cloudflare, but it does not explicitly state when to use this tool versus alternatives like scrape-dom. There is no direct exclusion or mention of better-suited sibling tools.

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