从入口 URL 广度优先抓取多页，每页转干净 Markdown（按实际抓取页数计费，每页 1 credit）。
纯抓取 + 格式转换，不生成任何 AI 内容；逐页 SSRF 校验，单页失败不中断。
| Name | Required | Description | Default |
|---|---|---|---|
| max_depth | No | 链接跟踪深度（0-3，0=只抓入口页） | |
| max_pages | No | 最多抓取页数（1-20） | |
| start_url | Yes | 入口页 URL（http/https，仅限公开网页） | |
| same_domain | No | 只跟踪同域名链接 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and discloses key behaviors: per-page billing (1 credit/page), pure crawling with no AI content, per-page SSRF checks, and non-interrupting failure handling. However, it omits details like rate limits, robots.txt handling, or exact output structure.
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 concise and front-loaded: two short paragraphs cover purpose, billing, security, and failure behavior without redundancy. Every sentence earns its place.
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 description provides a solid overview of behavior, billing, and resilience, but lacks a stated output format (e.g., list of {url, markdown} objects), which is important given there is no output schema to explain return values.
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?
The schema covers 100% of parameters with descriptions. The tool description does not add parameter-specific semantics beyond what is already in the schema, so the baseline of 3 is appropriate.
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 action ('从入口 URL 广度优先抓取多页，每页转干净 Markdown') with a clear resource (entry URL and multiple pages). It distinguishes from sibling tools like scrape_url (single-page) and site_map (site structure) by emphasizing multi-page crawling with Markdown conversion.
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?
The description clearly implies use for multi-page crawling tasks, but it does not explicitly mention alternatives or when not to use this tool. The context is clear overall, but exclusions are absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct role: site_map discovers URLs, scrape_url fetches a single page, crawl fetches multiple pages, and extract returns structured JSON. The overlap between scrape_url and crawl is clearly addressed in descriptions by single vs multi-page, so an agent can easily select the right tool.
The names are mostly intuitive, with two verbs (crawl, extract) and two noun phrases (scrape_url, site_map). The mix of verb and noun forms is a slight inconsistency, but all names are lowercase with underscores, so the pattern is still predictable.
With only 4 tools, each serves a distinct step in the web data workflow: discovery, single-page fetch, multi-page crawl, and structured extraction. This is an appropriate scope for the server's purpose, neither too sparse nor overwhelming.
The tool set covers the full pipeline from discovering URLs (site_map) to fetching content (scrape_url, crawl) to extracting structured data (extract). There are no obvious gaps for the server's stated purpose of web data collection and transformation.