web_crawl

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

With no annotations, the description must disclose behavioral traits. It only provides pricing and a free tier count, but omits crucial details like authentication requirements (the API URL suggests paid access), what the tool does with the URL (fetch HTML? scrape?), or any side effects. Minimal behavioral information.

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 very concise, consisting of two short lines. It front-loads the core action '网页爬取'. However, the inclusion of pricing and API endpoint adds length without aiding tool selection, slightly reducing efficiency.

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?

Given the single parameter with full schema coverage and no output schema, the description is incomplete. It does not explain what the tool returns (e.g., raw HTML, text, structured data), error scenarios, or limitations. Agents lack essential context for reliable 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?

The only parameter 'url' is fully described in the schema ('要爬取的URL'), so the description adds no further meaning. Baseline 3 applies due to 100% schema coverage.

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 '网页爬取' (web crawl), clearly indicating the tool's purpose of crawling a web page. However, it does not differentiate from sibling tools like web_search, which also fetch web content. The addition of '[Search]' suggests a category but not unique value.

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?

No guidance is provided on when to use this tool over alternatives. The description lacks any 'when to use' or 'when not to use' statements, and does not mention prerequisites or context.

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