search_products

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

No annotations are provided, so the description must carry the full burden. It describes basic behavior (search by keyword, return list with details) but omits potential behavioral traits such as authentication requirements, pagination behavior, rate limits, or whether the search is exact or fuzzy. The mention of 'affiliate URLs' is useful but not fully transparent.

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 two sentences, front-loaded with the main action ('Search for products on Coupang by keyword') and followed by concise details on return data and use cases. No unnecessary 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?

Given no output schema, the description adequately covers return fields and the keyword-based search. It also provides usage scenarios. However, it could mention pagination behavior or potential limitations (e.g., search accuracy). The sibling tools are related, but no cross-references are made.

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 coverage is 100% for both parameters (keyword and limit), so the schema already fully documents them. The description adds value by describing return fields (names, prices, images, affiliate URLs) but does not add meaning to the parameters 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 clearly identifies the tool as searching for products on Coupang by keyword, and it distinguishes itself from siblings like 'get_best_products_by_category' (category-based) and 'create_deeplinks' (link creation). It specifies the action (search) and resource (products) with a clear platform context.

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 says 'Useful for finding products, comparing prices, or discovering items,' which implies general usage scenarios but does not explicitly state when to avoid this tool or when to use a sibling tool instead. No exclusions or alternatives are mentioned.

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