Product detail (own browser)

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds value by revealing the extraction method (JSON-LD/embedded data first, implying web scraping) and that it opens a product page. This context goes beyond annotations without contradicting them.

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 purpose and key data points. Every word earns its place; no fluff or repetition. Highly efficient.

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 and a web scraping tool, the description lists extracted fields but does not describe the output format or structure. It also does not mention potential limitations (e.g., failure modes, rate limiting). Adequate but could be more 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?

The sole parameter 'url' has 0% schema description coverage. The description only says 'Open a Coupang product page,' which implies the url should be a product page, but it does not specify the expected URL format, whether relative/absolute, or what happens with invalid URLs. This provides little additional meaning beyond 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 clearly states the tool opens a product page and extracts specific details (price, rating, review count, delivery info), distinguishing it from sibling tools like search_products or get_product_reviews. The verb 'open' and 'extract' combined with the specific data points make the purpose highly unambiguous.

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 implies usage for obtaining details the official API cannot provide, but it does not explicitly state when to use this tool versus alternatives like get_product_reviews for reviews only. No 'when not to use' or prerequisite guidance is given.

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