Search + Parallel Extract

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds valuable behavior beyond this: per-page extract failures are isolated, cloud mode disables the tool, and mode affects token consumption. These details help the agent anticipate failure modes and cost, without contradicting any annotation.

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 three sentences, front-loaded with the core function, then elaborates on mode selection and constraints. Every sentence provides actionable information with no filler or repetition.

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?

The tool has an output schema, annotations, and a description that covers mode differences, token cost, failure isolation, and cloud limitation. This is complete for a combined search+extract tool with good structured metadata; nothing critical is missing.

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 100%, with detailed descriptions for all parameters including mode trade-offs. The description reinforces the mode semantics but does not add significant meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 opens with a specific verb+resource: 'One-shot Google search + parallel extract of the top results.' It clearly distinguishes this tool from siblings like search, search_parallel, and extract by combining both functions. The mode parameter is explicitly tied to the purpose, reinforcing clarity.

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 explicit guidance on when to use abstract vs full mode, including trade-offs on tokens and speed ('far fewer tokens', 'only when you need the actual article texts'). It also notes that the tool is disabled in cloud mode. It does not name sibling tools as alternatives, but the usage context is clearly implied.

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