scrape_as_html

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description usefully discloses anti-bot/CAPTCHA bypass behavior, but the phrase 'advanced options for content extraction' is misleading since the schema exposes only a single url parameter.

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?

Two sentences, front-loaded with the core action and result. Mostly efficient, though 'advanced options' is wasted filler that refers to nothing in 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, the description correctly states the return format (HTML). For a one-parameter tool this is nearly adequate, but the misleading 'advanced options' claim leaves the agent wondering about hidden configuration.

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 0% for the single url parameter. The description implies the URL is the sole input but adds no format, validation, or syntax detail beyond what the schema's 'format: uri' already conveys. Baseline 3 for a trivial single-param tool.

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?

States a clear verb (scrape) plus resource (single webpage URL) and output format (HTML). The 'single' and 'HTML' qualifiers implicitly differentiate it from scrape_batch and scrape_as_markdown, though no sibling is named explicitly.

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?

No when-to-use guidance is given. It never explains how to choose between this and scrape_as_markdown, scrape_batch, or extract, nor when HTML output is preferable to markdown.

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