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 full burden. It transparently describes the data returned (offers, specs, images, ratings, nextPageToken) and the effect of moreStores. It does not mention rate limits or authentication, but the read-only nature is clear from the title 'GET /' and the description's emphasis on retrieval.

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 concise: one paragraph starting with the primary action, then parameter explanations, then use cases. No wasted sentences, and the most important information is front-loaded.

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 no output schema, the description covers the main return fields (offers, specs, images, ratings, nextPageToken) and use cases. It lacks details on error handling, pagination limits, or prerequisite steps beyond having a pageToken, but overall it is sufficiently complete for a product detail tool.

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 descriptions already cover all 3 parameters (100% coverage). The description adds value by explaining the origin of pageToken, the default store count (3–5) and the effect of moreStores (up to ~13), and the pagination role of nextPageToken. This enriches understanding 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 'Get Immersive Product Information' and explains it expands a Google Shopping pop-up using a pageToken, returning detailed product data with offers. It distinguishes itself from siblings (e.g., general Google Shopping search, other data sources) by focusing on immersive product details.

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 lists explicit use cases: price-comparison bots, merchant discovery, dropshipping research, aggregating offers. It indirectly guides usage via the required pageToken parameter, but does not explicitly state when not to use or compare with siblings like google_serp_shopping_getSearchResults.

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