Google Immersive Product API

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

With no annotations provided, the description is the sole source of behavioral disclosure. It discloses that the operation is a retrieval ('Retrieve'), but gives no details about response behavior, error cases, or rate limits, and does not explain what 'immersive product popup' entails beyond the name.

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 a single sentence, front-loaded with the main action and resource, and contains no filler words. It is appropriately concise for its purpose.

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?

The tool has no output schema and no annotations, leaving the description to carry contextual weight, but it offers minimal information about the response format or how to obtain the page token. While the schema fully documents parameters, the description does not sufficiently compensate for the lack of output schema and behavioral context.

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?

The input schema covers 100% of the parameters with detailed descriptions, so the description does not need to add parameter information. The description mentions only 'page token' in passing and adds no additional semantic value 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 uses a specific verb 'retrieve' and specifies the resource 'detailed product info from Google's immersive product popup', which clearly distinguishes it from broader siblings like google_shopping and google_search. It also states the mechanism ('via a page token'), making the tool's function 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 implies usage through 'via a page token', indicating a prerequisite from a prior Google Shopping/Search response, but it does not provide explicit guidance on when to prefer this tool over alternatives like google_shopping or google_lens. There are no exclusions or alternative tool references.

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