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

The annotations already cover the read-only, open-world, idempotent, non-destructive profile, and the description adds useful behavior: output is raw HTML, requests go through ScrapingAnt's headless browser and rotating proxies. It does not mention rate limits or failure cases, but those are not required given the annotation coverage.

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 compact units: purpose, capability context, and a minimal invocation example. It is front-loaded and contains no filler, making it easy to scan before opening the schema.

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?

With no output schema, saying 'return its raw HTML' is essential and is present; the schema covers all parameter semantics. The main remaining gap is not pointing to the scrapingant_markdown/scrapingant_extract siblings or noting potential rate-limit/anti-bot failure behavior, but a successful call is fully preparable from this definition.

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 all seven parameters are already explained and the description does not need to compensate. The included example reinforces the url/browser/_apiKey call shape but adds no meaning beyond what the schema already 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 states a concrete verb and resource ('Scrape a web page') and names the output format ('raw HTML'), so an agent can tell what the tool produces. It also mentions headless rendering and anti-bot capability, though it does not explicitly distinguish itself from sibling scrapingant_markdown or scrapingant_extract.

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?

'Handles JS-heavy sites and anti-bot pages' gives a clear signal about when this scraper is the right choice. However, it never names alternatives or states when-not conditions such as choosing scrapingant_markdown for clean text or disabling the browser for static pages, so it is clear context without exclusions.

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