Search + Parallel Extract

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds useful behavioral details: per-page extract failures are isolated, disabled in cloud mode, and the trade-offs between abstract and full modes. No contradiction with annotations.

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 concise (3-4 sentences) and front-loaded with the primary action. Every sentence adds value: main function, default behavior, mode switch guidance, failure handling, and cloud mode restriction. No waste.

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 that an output schema exists and schema coverage is 100%, the description is fairly complete. It explains the return format (SERP with abstracts), failure isolation, and mode behavior. Minor missing details about error handling or the exact output structure, but overall sufficient.

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 coverage is 100%, so baseline is 3. The description adds significant meaning beyond the schema: explains the purpose of 'mode' (abstract vs. full), default values for max_chars based on mode, and the limit range with defaults. This enriches the parameter understanding.

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 it performs a 'one-shot Google search + parallel extract of the top results,' using a specific verb and resource. It distinguishes from siblings like 'search' (likely just returns links) and 'extract' (maybe single page) by mentioning parallel extraction and modes.

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 guidance on when to use each mode (abstract vs. full) based on token cost and speed. However, it does not explicitly differentiate this tool from its sibling 'search_parallel' or state when not to use it in favor of another tool.

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