google_serp_immersive_product: GET /

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

No annotations are provided, so the description carries the full burden. It discloses what is returned (offers, specs, images, ratings, nextPageToken) and the moreStores expansion behavior, which is useful. However, it does not mention pagination mechanics, error cases, response size, or any limits, leaving behavioral gaps for a tool with zero annotation coverage.

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?

A single information-dense paragraph that front-loads the core action and parameter semantics. No wasted sentences, though it packs many return fields into one long clause that could be lightly restructured for scanability.

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?

With no output schema and no annotations, the description lists the return content and parameter behavior, covering the essential call context. It is reasonably complete for a read-style tool, though it omits error handling and prerequisite clarification beyond the token requirement.

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%, which sets a baseline of 3, but the description adds real value on top: it quantifies moreStores ('up to ~13 merchants instead of 3-5') and explains nextPageToken's role in paginating stores. This enriches the schema's terse definitions meaningfully.

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 names a specific verb ('Expands the Google Shopping Immersive Product pop-up') and resource, clearly distinct from the siblings (search results, AI mode, events, news). An agent can tell this tool apart immediately because it is the only one tied to the immersiveProductPageToken pop-up expansion.

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?

Lists concrete use cases ('price-comparison bots, merchant discovery, dropshipping research, aggregating full offer lists'), giving clear context on when to call it. It stops short of explicit exclusions or 'when not to use' routing to alternatives, which would make it fully complete.

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