google_serp_shopping: GET /

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

With no annotations provided, the description carries the full burden. It discloses the response fields (product title, price, merchant/source, rating, etc.), the filtering mechanism via shoprs and hasdata_link, and pagination via start. It also mentions that tokens can be fed into the Immersive Product API. It does not mention rate limits or auth, but those are often outside tool descriptions. The GET method in the title implies read-only, and the description aligns. It adds substantial behavioral context beyond the schema.

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 paragraphs, efficiently front-loading the purpose and then detailing output fields and use cases. It avoids redundancy and keeps each sentence informative. Slightly longer than necessary but still well-organized and easy to scan.

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 tool's complexity (10 parameters, nested filter structure, pagination), the description covers the essential information: what it returns, how to use filters, and how to connect to downstream APIs. It lacks explicit error handling or rate limit info, but for an agent selecting and invoking the tool, the provided context is sufficient for correct usage.

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%, so each parameter is already well-documented in the schema. The tool description adds some high-level context (e.g., 'offset pagination' for start, 'shoprs filter-helper IDs' for shoprs, 'location/uule' for location), but it does not significantly deepen the meaning beyond what the schema already provides. It meets the baseline for high coverage.

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 scrapes Google Shopping listings for a query, and lists specific filters and return fields. It distinguishes itself from sibling tools by explicitly focusing on 'Shopping Search Results' as opposed to general SERP, news, events, etc. The verb 'Get' and resource 'Shopping Search Results' are specific and unambiguous.

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 use cases: e-commerce price tracking, catalog building, promotion discovery, and feeding productIds into the Product API or tokens into the Immersive Product API. It does not explicitly state when NOT to use it or compare to alternatives, but the use cases are sufficiently contextual to guide an agent. It lacks explicit exclusions or mention of sibling tools, so it stops short of a 5.

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