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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a meaningful piece of behavioral context the schema cannot: a cost of 30 points per call, which directly affects invocation decisions. It stops short of describing failure modes (e.g., invalid/non-brand-store URLs).

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?

Front-loaded with the resource and return fields, and the cost note is placed at the end. The bilingual English/Korean duplication roughly doubles the text for the same content, which is a minor redundancy but justified for a Korean-market tool.

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?

For a single-parameter read-only tool with no output schema, the description covers source scope, returned fields, and cost. It is nearly complete; only edge-case behavior for malformed or non-brand-store URLs is unaddressed.

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?

Only one parameter, and schema coverage is 100% with the URL format and an example already documented in the schema. The description's 'by URL' phrasing adds no syntax detail beyond what the schema provides, 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?

States a specific verb (retrieve) and resource (Naver brand store product) scoped by URL, and enumerates exactly which fields come back (title, prices, discount, reviews, sellers, product info, tags, images). The 'Naver brand store' qualifier cleanly distinguishes it from siblings like amazon_product and coupang_product.

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 nothing about when to choose this tool over the other product-retrieval siblings (amazon_product, coupang_product) or when a URL is out of scope. Usage is only inferable from the name; no explicit conditions or alternatives are given.

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