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

Even with annotations already declaring readOnlyHint and openWorldHint, the description adds meaningful behavioral detail: it routes through ScrapeUnblocker, bypasses anti-bot systems (Cloudflare, DataDome, PerimeterX, Akamai, Shape), requires a real browser, and returns raw rendered HTML. The step-based interaction model is also disclosed, and nothing in the description contradicts the annotations.

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 compact and front-loaded: purpose, use condition, return type, and step guidance are covered in a few dense sentences before the schema takes over. Every sentence adds information rather than repeating the schema or annotations.

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?

For a tool with one required parameter and no output schema, the description tells the agent what is returned (raw HTML), when to use the tool, and how to prepare interactions. The schema covers remaining parameter details and failure behavior (422 with step name and HTML), so nothing critical is missing for correct invocation.

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 baseline is 3. The description adds practical value for the main nontrivial parameter, `steps`, by explaining its purpose ('search, click, paginate') and directing the agent to use list_elements first for selector discovery. Other parameters like proxy_country and sleep_seconds remain schema-only, which is acceptable at full coverage.

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 opens with 'Fetch the fully rendered HTML of any web page', naming a specific verb, resource, and output. It also distinguishes itself from sibling fetch_parsed by emphasizing 'fully rendered' and 'raw HTML', and from google_search by targeting arbitrary pages rather than search results.

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?

It explicitly states when to use the tool: 'Use when a normal fetch is blocked (403/429, captcha) or the page needs a real browser.' It also advises using list_elements first to discover selectors. However, it does not explicitly name fetch_parsed as the alternative for when parsed content is preferred, though 'Returns raw HTML' implies that choice.

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