scrape_batch

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

No annotations are supplied, so the description carries the full burden. It does disclose two valuable behaviors — a hard cap of ten URLs and that credit/balance is consumed and reported — but it omits auth requirements, per-URL failure handling, whether partial results are returned, and any rate limits.

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 front-loaded sentence with no filler; the batch cap and return payload arrive immediately. Its brevity is efficient, though the same terseness is the source of the missing parameter guidance.

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 two-parameter tool with no annotations, no output schema, and 0% schema coverage, the description covers only the URL count and return summary. The render parameter, URL validity rules, and failure behavior are all absent, so an agent cannot invoke it confidently beyond the simplest case.

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%, so the description must compensate and does not. It covers 'urls' implicitly via the ten-URL limit, but the 'render' enum (auto/always/never, default 'never') is never mentioned, leaving the agent no way to know when JavaScript rendering is needed.

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 ('Scrape') and resource ('public URLs') plus a concrete batch ceiling of ten, which distinguishes it from the single-page sibling scrape_page without naming it. The return content ('each status and the remaining balance') further pins down what the call produces.

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 'up to ten' limit implies batch usage and 'public' implies an access restriction, but there is no explicit when-to-use or when-not guidance, and no routing between this and scrape_page for single-URL work. The agent must infer the boundary from the name and the number ten.

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