fetch_multiple_contents

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

With no annotations, the description carries the full behavioral burden. It discloses parallel fetching, max batch size, non-blocking behavior, timeout and max_length constraints, but does not explain partial failures, per-URL error handling, auth/rate limits, or what 'non-blocking' means operationally.

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 opening sentence is front-loaded and efficient, followed by structured Args and Returns sections. It is appropriately sized, though the Returns section is somewhat redundant because an output schema exists.

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 an external-fetch tool with no annotations, the description covers the key batch and parameter constraints and summarizes the return shape. However, it omits error semantics, partial-failure behavior, and content extraction limitations, leaving meaningful gaps for correct invocation in failure cases.

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 it does: it defines urls as required with max 10, timeout in seconds with range 5-30 and default 10, and max_length per URL with range 100-20000 and default 2000. It adds useful ranges and meaning beyond the bare schema, though URL formatting/validation is not addressed.

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: fetch and extract content from multiple URLs, with parallel execution and a max batch of 10. It is distinguishable from fetch_content by the plural/parallel batch behavior, though it does not explicitly name the sibling as the single-URL 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?

Provides practical constraints such as max 10 URLs and non-blocking behavior, but gives no explicit guidance on when to use this versus fetch_content or search tools. Usage is implied by the batch nature rather than stated as routing guidance.

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