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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context the annotations do not: results are sponsored/ad-funded rather than organic, and it mentions total page count as part of the payload. It stops short of rate-limit, freshness, or ordering/pagination behavior.

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?

Two sentences, front-loaded with the returned fields and closing on the sponsored-content caveat. No filler; each clause carries information.

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?

A simple two-parameter, read-only search tool with an output schema that already covers return shape; the description adds the important sponsored-vs-organic framing. Only the missing explicit when-to-use/alternative naming keeps it from being fully complete.

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%, so the schema already documents 'q' and 'region'. The description adds nothing about parameter syntax, accepted values, or how region affects results, so 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?

The description enumerates the returned fields (title, brand, merchant, price, rating, review count) and characterizes the resource as 'shopping results', and it explicitly distinguishes itself from organic content. It never states the action verb ('search'), but the name plus the listing of normalized fields makes the distinct scope clear against duckduckgo_search.

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 explicit when-to-use or when-not guidance, but 'Sponsored/ad-funded product listings, not organic content' implies the condition that selects this over duckduckgo_search for product/purchase intent. The alternative is not named, so the routing must be inferred.

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