fetch_many

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes key behaviors like parallel fetching, content extraction, citation formatting, and automatic/manual rendered modes, but doesn't cover important aspects like error handling, rate limits, authentication needs, or what happens when URLs fail.

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 perfectly concise with two sentences that each earn their place. The first sentence establishes core functionality, the second provides important behavioral nuance about rendered mode. No wasted words.

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 complex tool with 7 parameters, no annotations, and no output schema, the description provides good high-level context about what the tool does but leaves significant gaps in parameter documentation and behavioral details. It's adequate for understanding the tool's purpose but insufficient for confident usage.

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?

With 0% schema description coverage and 7 parameters, the description only mentions the 'rendered' parameter explicitly. It doesn't explain what 'max_excerpt_chars', 'max_links', 'render_wait_ms', 'concurrency', or 'ttl' do, leaving most parameters semantically undocumented.

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 purpose with specific verbs ('fetch multiple URLs in parallel', 'extract content', 'return compact citations') and distinguishes it from siblings by mentioning parallel fetching and automatic rendered fetch for JS-heavy pages, which suggests different capabilities than simpler fetch tools.

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 provides clear context for when to use rendered mode ('set rendered=True to force browser mode') and implies usage for batch URL processing, but doesn't explicitly state when to choose this tool over siblings like fetch_url or search_and_fetch, nor does it mention exclusions.

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