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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds two useful pieces beyond that: the exact result fields (compensating for the absent output schema) and a per-call cost note '[호출당 5포인트]', which is real behavioral context an agent should weigh. It omits pagination behavior despite the page parameter, keeping it short of a 5.

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?

Core purpose is front-loaded in the first sentence, with output fields and cost trailing efficiently. The bilingual Korean duplication repeats identical content, which is justified for a Korean-language service but is redundancy nonetheless, keeping it from a 5.

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 simple two-parameter search tool this is largely complete: it states the return fields (important since no output schema exists), the cost, and the parameter intent, while annotations cover the read-only/open-world nature. Pagination semantics and any result-count limits remain unstated.

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 both keyword and page already documented (including the 1~10 page range), so the schema does the heavy lifting. The description only echoes 'for a keyword' and adds no format or constraint detail beyond the schema. Baseline 3 is appropriate.

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 gives a specific verb and resource ('Google Shopping search: return product results ... for a keyword') and even enumerates the returned fields, so the tool's function is unmistakable. It does not, however, distinguish itself from the many sibling search tools (google_search, google_image_search, google_news_search, google_lens_search), leaving that separation to the tool name alone.

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?

There is no when-to-use guidance and no named alternative. An agent scanning the large sibling set of Google search tools gets no signal about when Shopping is preferred over general, image, or news search. The purpose statement implies a product-search use case but stops short of routing guidance.

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