web_batch

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

With no annotations, the description carries the burden and does add useful behavior: concurrency, full processing chain per URL, per-URL token limits, and a batch default of 20. It does not cover failure handling, rate limits, or clarify what '完整分级链路' actually entails.

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 compact, front-loaded with the core behavior, and uses a clear argument list with no filler. Each sentence contributes meaningful information.

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?

For a three-parameter tool with an output schema present, the description covers the essentials: target URLs, per-URL token budget, link policy, and result granularity. It is incomplete in that it omits error semantics, behavior when the batch limit is exceeded, and the precise meaning of the full processing chain.

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%, but the description compensates well by defining all three parameters: urls with a maximum/default count, max_tokens as a per-URL budget, and link_policy as equivalent to web_fetch. It loses one point because 'batch_max_urls' is referenced but not fully explained and link_policy values are not expanded.

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 verb and resource: '并发抓取一批 URL' (concurrently fetch a batch of URLs) and notes that results are returned per URL. This is clear and the batch name distinguishes it from web_fetch, though it does not explicitly contrast the two siblings.

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 batch behavior implies use for multiple URLs versus web_fetch for a single URL, and link_policy is explicitly delegated to web_fetch semantics. However, it does not state when to prefer this tool over web_fetch or mention alternatives.

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