Get SERP results

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

With no annotations, the description fully carries the behavioral transparency burden. It discloses task creation, polling interval (5s), timeout (5 min), result types, and progress notifications. This provides sufficient behavioral insight for an agent.

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-loads the purpose, and avoids unnecessary details. Every sentence serves a clear function: stating what it does, how it works, and what it returns.

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 lack of output schema and the presence of 9 parameters, the description adequately covers core behavior but omits details about the return structure or parameter relationships (e.g., language_code, location_id). It is moderately complete.

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 does not add significant new meaning beyond the schema's parameter descriptions. For example, 'result_type' is explained the same in both places.

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 runs a SERP query and returns results, specifying organic/ads/featured snippets for standard and all types for advanced. It distinguishes the tool from siblings like DATA_getSerpHtmlDump or DATA_getSerpTasks by mentioning task creation and polling.

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?

While it describes the result types, it does not provide explicit guidance on when to use this tool versus other SERP-related siblings (e.g., getSerpHtmlDump, getSerpTaskResults). The usage context is implied but not contrasted with alternatives.

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