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

With no annotations, the description carries the full burden. It does disclose two genuinely useful behavioral traits: the return shape (prices, sellers, ratings, links) and the per-call cost ($0.015). It says nothing about rate limits, auth requirements, or result pagination beyond the schema's own limit cap.

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?

Three short sentences, front-loaded with what the tool is, then what it returns, then what it costs. Every sentence earns its place and nothing is padded.

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?

For a two-parameter search tool with no output schema, the description covers purpose, return fields, and cost — enough for an agent to call it correctly. The remaining gap is routing guidance relative to the many sibling search_* tools, plus pagination behavior at the 20-result cap.

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% with only two parameters, both documented in the schema including the limit maximum of 20. The description adds no syntax, format, or interpretation guidance for query or limit, so the baseline 3 applies.

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?

States a specific verb+resource combination ("Google Shopping product search") that is immediately distinguishable from search_web, search_images, and search_places. It never names a sibling or states its distinguishing boundary explicitly, but the domain qualifier does the disambiguation work implicitly.

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?

No when-to-use or when-not-to-use guidance. Nothing tells the agent to prefer this over search_web for product queries, or whether it covers local/in-store pricing the way search_places might. Usage must be inferred entirely from the word "Shopping" in the purpose statement.

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