fetch_many

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that each link passes an SSRF guard and that one failed page does not fail the whole batch, which is important operational context. However, it does not state authentication requirements, rate limits, or the read-only nature of the operation explicitly, leaving meaningful behavioral gaps for a network-fetching tool.

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 lines, front-loaded with purpose, then WHEN, NOT WHEN, and a behavioral note. Every sentence earns its place and nothing is repeated unnecessarily.

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?

Usage guidance is complete and output schema exists so return values need not be described. However, for a three-parameter tool with 0% schema description coverage, the description omits parameter meanings and limits, especially max_chars and max_pages, which an agent needs in order to invoke the tool correctly.

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 for missing parameter documentation. It only indirectly implies the urls parameter by mentioning links, and says nothing about max_chars or max_pages, both of which have defaults and affect behavior. This leaves two of three parameters undocumented in any human-readable form.

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: reading a batch of pages in one call. It also distinguishes from the sibling tool fetch_page by naming the single-page alternative. An agent can tell exactly what it does and how it differs from fetch_page.

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?

Explicit WHEN / NOT WHEN structure: use when gathering N sources at once, do not use when one page is needed, and route to fetch_page. The condition that selects the alternative is stated plainly with no inference required.

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