scrape_multiple

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions 'in parallel' and 'return results for each,' but fails to specify error handling, concurrency limits, side effects, or any authentication requirements. Key behavioral information is missing.

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 consists of two concise sentences front-loaded with the core purpose. Every sentence adds value with no unnecessary words, making it efficient and easy to parse.

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 tool has 5 parameters and no output schema, the description is too brief. It does not explain the return format (e.g., structure of individual results) or differentiate from the sibling 'scrape_url' (which may have similar parameters). The parameter booleans remain undefined, leaving significant gaps for the agent.

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 input schema has 20% description coverage (only 'urls' is described). The tool's description adds no additional parameter meaning beyond the schema, leaving the booleans (extract_text, extract_links, etc.) unexplained. The agent lacks understanding of how these parameters affect scraping behavior.

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 'Scrape multiple URLs in parallel and return results for each,' which is a specific verb and resource. It implicitly distinguishes from the sibling 'scrape_url' by highlighting parallel execution for multiple URLs, but does not explicitly name the alternative.

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 explicitly provides a use case: 'Use when you need to compare or aggregate data from several pages.' This gives clear context for when to use the tool. However, it does not mention when not to use or suggest alternative tools.

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