Fetch multiple Gemini resources

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

Annotations already provide readOnlyHint and openWorldHint. Description adds valuable behavioral details: uses asyncio.gather for concurrency, returns results in same order, and caps at 50 URLs. No contradictions.

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?

Description is concise, using docstring structure with Args and Returns sections. Every sentence adds value, no redundancy. Key info is front-loaded.

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 output schema existence, description covers input behavior (parallel, limit), return structure (list same order), and use case. No notable gaps; sibling tools provide additional context.

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 has 0% description coverage. Description provides crucial parameter semantics: 'List of Gemini URLs to fetch (at most 50 per call)', adding meaning beyond type and array items schema.

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?

Description states 'Fetch multiple Gemini URLs in parallel for improved performance', clearly identifying action (fetch), resource (Gemini URLs), and key differentiator (multiple, parallel). This distinguishes from sibling gemini_fetch (single) and gopher siblings (different protocol).

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?

Description explains use case (multiple URLs, parallel speed improvement), includes constraint (at most 50), and implies sequential alternative. However, it lacks explicit 'when not to use' or direct reference to alternative sibling tools.

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