Search Coupang products (own browser)

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

The description adds behavioral context beyond the readOnlyHint and openWorldHint annotations by specifying that the tool opens the search page in the user's own Chrome and requires a remote debugging port. This clarifies the non-API nature and the reliance on the user's browser state.

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 extremely concise with three sentences, each adding essential information: the action, the no-API-key note, and the prerequisite. There is no redundancy or filler text.

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 the lack of an output schema, the description should ideally mention what the tool returns (e.g., search results or product list). It covers usage context and prerequisites but not the result format or pagination behavior, leaving a notable gap.

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 schema has 0% description coverage, and the description does not explain any of the four parameters (keyword, limit, sortBy, rocketOnly). The agent must infer meaning from parameter names and type/enum constraints, which are somewhat self-explanatory but lack explicit guidance.

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 states the tool searches Coupang by opening the search page in the user's own Chrome browser, which is a specific verb-resource combination. The title also mentions 'products', and the description distinguishes it from sibling tools like add_to_cart and get_product_detail by focusing on the search function.

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 explains that no API key is needed and that Chrome must be running with a specific debugging port, providing prerequisites. However, it does not explicitly state when to use this tool versus alternatives, such as API-based searches, or when not to use it.

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