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

With no annotations, the description carries the full burden of behavioral disclosure, but it only reveals the output format and per-call price. It does not mention whether the scraper executes JavaScript, how it handles dynamic pages, rate limits, redirects, or any limitations that would matter for choosing this tool.

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 a single, compact sentence that front-loads the action and output, then appends the cost. Every word earns its place, and there is no redundant or filler 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?

For a tool with no annotations and no output schema, the description is too sparse to be fully actionable. It states the return format but omits usage boundaries, behavioral limitations, and how it relates to sibling tools like browser_scraper, leaving important decisions to inference.

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%, so the description must compensate, but it adds no detail about the url parameter besides implying it points to a web page. It does not explain URL formats, protocols, or any constraints beyond the schema's basic string type.

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 identifies the action ('Scrapes web pages') and the output ('clean markdown'), making the tool's purpose understandable at a glance. However, it does not distinguish web_scraper from the similarly named sibling browser_scraper, so the differentiation is incomplete.

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?

There is no guidance about when to use web_scraper versus browser_scraper, extract_json, render_screenshot, or pdf_extractor. The description implies plain web-to-markdown conversion but gives no exclusions, prerequisites, or alternative-selection criteria.

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