scrape_dynamic

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

No annotations exist, so the description carries the full behavioral burden, and it discloses only that a headless Playwright browser is used. It says nothing about runtime (browser automation is slow), whether JS evaluation is executed in a sandbox, what the screenshot/asset handling looks like, or what happens when selectors fail — all material for a 9-parameter browser-driving 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?

A single sentence with zero filler, and the distinguishing qualifier ('dynamic SPA') is placed immediately after the verb-resource pair. It is well-formed but so short that there is no structure beyond that one clause — nothing is wasted, but little is delivered.

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?

An output schema exists, so return values need not be described, but everything else is missing: no guidance distinguishing it from scrape_url/deep_crawl/scrape_batch, no explanation of the 9 knobs, and no caveats for JS execution or headless-rendering failure. For a browser-automation tool with this much surface area, the description is far from sufficient.

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 9 parameters, so the description must compensate and it does not. Parameters like evaluate_js (arbitrary code execution), scroll_depth (units? pages? steps?), click_selector, and wait_for_selector are unexplained in both schema and prose, leaving the agent to guess semantics and defaults behavior.

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 gives a specific verb ('Scrape') plus a precisely scoped resource class ('dynamic Single Page Applications (React, Vue, Next.js)') and names the enabling mechanism (Playwright headless browser). It implicitly separates itself from scrape_url by targeting JS-rendered pages, but never names that sibling explicitly, so the differentiation is left to inference.

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?

Usage is only implied: an agent can infer 'use this when the page needs JavaScript to render.' There is no explicit when-not condition (e.g., prefer scrape_url for static HTML, search_and_scrape for query-plus-fetch) and no mention of cost, latency, or failure modes that would influence tool selection among the many scraping siblings.

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