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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context — the 30-day history window, the today-vs-30-day scope, and the 'independent comparison service, not affiliated with sellers' disclaimer — but says nothing about unknown-seller behavior or failure modes.

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 same content is written twice, once in English and once in Korean, roughly doubling the length with zero new information. It also leads with a laundry list of metrics instead of a front-loaded statement of what the tool is, so the purpose is buried behind output detail.

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?

With no output schema, the description must carry the return-value burden, and it does describe the returned metrics in detail. However, it omits sibling disambiguation and any indication of what happens with an unrecognized seller, which leaves gaps for a tool whose neighbor get_price_trend sounds like a plausible substitute.

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 description coverage is 100% and the single 'seller' parameter already carries an enum-like example list (말톡, 도시락이심, 유심사스토어), so the schema does the heavy lifting. The description never mentions the input parameter at all, adding no meaning beyond the schema; 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?

The description states the resource precisely (an eSIM seller's operational profile) and enumerates the specific metrics returned: price-change frequency, sold-out option ratio, cheapest country/day cells, and official-vs-Naver price cross-check. The verb 'get' is implied rather than stated, and it never distinguishes itself from the adjacent sibling get_price_trend, which the 'how often a seller changed prices' metric overlaps with.

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?

There is no when-to-use guidance at all. An agent cannot tell from this text whether to call get_seller_profile, get_price_trend, or find_esim_prices for a given price question, and no prerequisite (e.g., a valid seller name) is mentioned.

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