Parallel Search with selectable mode

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds mode selection context, but it also makes a misleading claim: 'Defaults to turbo' whereas the schema explicitly states that Chinese uses basic when mode is omitted. This inaccuracy reduces transparency and could mislead an agent, plus no other behavioral traits (rate limits, pagination) are disclosed.

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 two sentences and extremely concise, front-loading the purpose and then providing mode guidance. Every word earns its place with no filler or redundant information.

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 presence of a rich input schema, annotations, and an output schema, the description is adequate but not complete. It clearly states the tool is for web search, but it fails to clarify the language-dependent default behavior (contradicting the schema), and does not mention how this tool relates to parallel_fetch. The gaps are notable but not severe because the schema covers most operational details.

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 56%, but the tool description adds minimal value beyond the schema. It mentions mode names ('turbo', 'basic', 'advanced') and a default, but these are already documented in the mode parameter. Undocumented parameters like session_id, max_results, exclude_domains, and include_domains receive no clarification from the description, so it does not compensate for the coverage gap.

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 identifies the tool's purpose: 'Search the web through Parallel Search API.' This is a specific verb+resource pairing that makes the primary function obvious. It does not explicitly distinguish itself from the sibling tool parallel_fetch, but the word 'Search' versus 'fetch' implies a distinction.

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 some usage context by explaining the default mode and suggesting to 'select basic or advanced when needed.' However, it gives no explicit guidance on when to use this tool versus the sibling parallel_fetch, nor does it mention any exclusions or prerequisites. The usage context is implied but not fully developed.

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