Scrape a web page to Markdown

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

Discloses automatic escalation from HTTP to browser with stealth proxies for JS rendering and bot detection bypass. No annotations present, so description carries full burden; missing potential failure or rate limit info.

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 main purpose, no fluff. Every sentence adds necessary context.

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?

Covers purpose, usage, behavior, and parameter details adequately for a simple fetch tool without output schema. Could mention error handling or timeouts.

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 coverage is 100%, baseline 3. Description adds value by explaining 'render' enum behaviors (auto, http, browser) and 'onlyMainContent' default, going beyond schema.

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?

Clearly states the tool fetches a single URL and returns LLM-ready Markdown. Distinguishes from siblings 'crawl' and 'screenshot' by specifying single-page focus and output format.

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?

Explicitly says 'Use for docs, articles, product pages, SPAs, or any single page,' providing clear context. Lacks explicit exclusions but effectively implies appropriate use cases.

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