Search retail products

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

No annotations are provided, so the description carries the burden. It discloses live-data nature and cross-country comparison behavior, which is relevant. However, it does not describe return format, pagination, rate limits, or other side effects. For a simple search tool, this is adequate but not comprehensive.

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 concise sentences, front-loaded with the core purpose. Each sentence adds specific, non-redundant information about scope and capabilities. No wasted words.

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 description covers the main search scopes and the optional countryCode behavior, which is critical for correct invocation. However, without an output schema, it does not clarify what fields are returned or pagination, leaving some ambiguity for the agent. Overall adequate for a straightforward search 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?

The description adds meaningful context to the retailer enum (explaining what each retailer covers) and countryCode (supporting cross-country price comparison), which goes beyond the schema's sparse enum and default. The query parameter already has an example in 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 opens with a specific verb and resource ('Search live product data from a retailer'), then clarifies the two retailer domains (beauty, furniture/home goods). This clearly distinguishes it from sibling tools focused on real estate and locations.

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 provides clear context for when to use the tool (searching Sephora or IKEA products), including geographic coverage and countryCode usage for price comparisons. It does not explicitly name alternatives, but the retailer-specific coverage implies usage boundaries and differentiates from unrelated siblings.

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