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 useful behavioral context beyond that: the data is a 7-day rolling purchase count scraped daily from Naver, the ranking is externally determined, and each row carries share %, typical nights, and a 30-day median comparison. It does not cover freshness lag or update timing, but the added context is substantial.

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 English statement is front-loaded and dense with no filler, followed by a faithful Korean mirror for the Korean-language audience. The bilingual duplication doubles the length, but the content is non-redundant in meaning and each sentence carries information.

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?

There is no output schema, so the description properly compensates by enumerating the returned fields (share %, typical nights, 30-day median comparison) and the aggregation level. The main remaining gap is the relationship between the limit parameter and pagination/ordering, but for a simple two-parameter read tool this is nearly 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?

Schema description coverage is 100% and the enum parameter carries its own Korean description, so the schema does the heavy lifting. The description echoes the city-vs-country dimension but adds no syntax, default, or format detail beyond what the schema already states, making 3 the correct baseline.

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 names a specific resource (a daily demand index for Korean outbound package tours) and states precisely what is measured and how (sum of 'N people bought in the last 7 days' shown on Naver package-tour product pages, aggregated to city/country). It also disclaims the ranking authority ('Ranking is set by Naver buyers, not by us'), which cleanly separates it from sibling tools like get_tours or list_popular_packages.

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 makes the tool's domain obvious (demand ranking data) so usage is implied, but it never states when to pick it over get_tours, list_popular_packages, or get_series_history, nor any exclusions or prerequisites. No explicit when/when-not guidance is present.

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