Google Search Parallel

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

Beyond the readOnlyHint annotation, the description discloses several critical behaviors: internal rate limit (~10/min), first-call warmup (5-10s), per-query failure isolation, and cloud-mode disabling. This significantly exceeds what annotations alone provide.

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 sentences, each carrying essential information. The main action is front-loaded, and there is no filler or repetition of schema details.

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 description covers key behavioral constraints, rate limits, failure handling, and environment restrictions. An output schema exists, so return-value explanation isn't necessary. Minor inconsistency between schema minItems (1) and description (2-10) is a schema issue, not a description gap.

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% for both parameters, so the schema already explains 'queries' and 'limit'. The description reinforces the 2-10 query count and adds rate-limit context, but doesn't add new parameter-level meaning beyond the 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?

The description clearly states the action: 'Run 2-10 Google searches concurrently.' It identifies the resource (Google searches) and the specific parallel capability, distinguishing it from the sibling 'search' tool.

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 a clear use case ('compare multiple angles in one call') and an explicit when-not-to-use ('do not loop this for bulk scraping'). However, it doesn't explicitly name an alternative tool for single searches, so it misses the full 'alternatives' criterion for a 5.

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