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

With no annotations, the description carries the full behavioral burden and does well: it discloses the async job model (returns a jobId, must be polled), upfront per-url charging, and that failed and cache-served urls are refunded. It does not cover auth requirements or rate limits, which is a minor gap.

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?

Four short sentences, zero waste, with the core action, the explicit exclusion, the billing model, and the polling requirement each front-loaded in turn. Nothing is padding.

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 an async batch tool with no output schema, the description supplies the essential contract: input shape, returned handle (jobId), cost model, and the required status-polling tool. Only fine details like job-id lifetime or partial-failure semantics are absent, which is acceptable given the sibling status tool exists.

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 100%, so the schema already documents every parameter including the nested json/wait objects. The description reinforces the url count range (2 to 50) and site-agnosticism plus cache pricing, but adds little syntax beyond what the schema states. Baseline 3 applies.

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?

States a specific verb and resource ('reads a list of urls... returns a jobId') and explicitly distinguishes itself from the sibling web_crawl by noting it 'discovers nothing on its own.' An agent can separate this from web_scrape and web_crawl without opening a schema.

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?

Gives both the when (batch read of a user-supplied url list) and the when-not ('for that use web_crawl'), plus the required follow-up action ('Poll it with web_batch_status'). The alternative and the next step in the workflow are both named.

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