scrape_url

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

With no annotations, the description carries the full behavioral burden. It usefully discloses 'browser fingerprinting' (implying anti-bot evasion) and the Markdown output form, but says nothing about what happens on blocked/failed requests, whether JavaScript is rendered, rate limits, or whether the scrape is subject to robots/permission constraints.

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?

A single sentence, front-loaded with the action and resource, and every clause earns its place by naming the distinguishing output behavior. No filler or repetition of 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?

There is no output schema and no annotations, so the description is the only source of behavioral information. It covers the core purpose adequately but omits failure modes, blocking behavior, and any indication of cost or latency, which matter for a scraper that relies on fingerprint evasion.

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%: url, timeout, and extract_markdown are all documented in the schema with types and defaults. The description adds no syntax or format detail beyond that, so the baseline of 3 applies.

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 specific verb+resource ('Scrape a web page') and adds the output transformation ('convert its content into clean, token-efficient Markdown'), so the agent knows exactly what it produces. It does not explicitly contrast itself with the siblings extract_links and extract_metadata, which an agent would need to choose among for a given page.

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 when-to-use guidance, no mention of prerequisites, and no routing to alternatives. The siblings extract_links and extract_metadata are never referenced, so selection between the three tools is left entirely to inference.

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