scrape_url

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

With no annotations, the description carries the behavioral burden but discloses little beyond ad removal and Markdown conversion. It does not explain caching and forced refreshes, engine selection, waiting or rendering behavior, truncation, access limitations, or failure behavior.

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 single sentence is front-loaded, easy to scan, and free of filler. However, its brevity omits important operational detail for an 11-parameter tool, and "any website" is an unqualified, overly broad claim.

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?

The output schema reduces the need to describe return values, but the definition remains incomplete for a complex tool with undocumented parameters, no annotations, and many close siblings. It supplies the core value proposition but not enough context for reliable selection and 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 0% across 11 parameters, and the description documents none of them. "Ad-free" loosely relates to strip_ads, but there is no guidance for engine, max_chars, css_selector, wait_seconds, cache controls, or the inclusion flags.

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 provides a clear action ("Scrape"), resource ("any website"), and result ("clean, ad-free Markdown"). It does not differentiate this general scraper from siblings such as scrape_dynamic, scrape_batch, or extract_structured.

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 explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent cannot tell whether this is intended for static pages, JavaScript-rendered pages, batch work, or crawling rather than the relevant sibling tools.

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