Scrape multiple URLs concurrently (cost-aware)

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

With no annotations, the description must carry the burden. It discloses the parallel execution, 'free-first' routing, and the return object shape. However, it omits details about failure handling, rate limiting, or cost implications beyond the 'paid' field, and it relies on referencing smart_scrape for routing details.

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 two sentences long, front-loaded with the core action, includes the return format, and gives usage guidance. Every sentence adds value with no redundancy.

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 batch tool with 7 parameters, no output schema, and no annotations, the description is incomplete. It explains the return format and usage context but leaves parameter semantics and edge-case behavior undocumented, which is needed for a tool of this complexity.

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 low (29%), and the description does not explain the non-URL parameters like free_only, concurrency, data_format, or rate_limit_ms. It hints at free-first routing and concurrency, but the agent cannot accurately set parameters without additional documentation.

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 clearly states the tool's function: fetching an array of URLs in parallel, with the same routing as smart_scrape. It explicitly distinguishes itself from calling smart_scrape in a loop, making its purpose unambiguous.

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 gives explicit guidance: use this instead of calling smart_scrape in a loop for better performance. It references the sibling smart_scrape for routing behavior but does not mention exclusions or alternative tools like smart_crawl for broader crawling tasks.

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