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

With no annotations, the description carries the full burden, and it discloses one genuinely useful behavioral trait: a hard rate limit of 10 free calls/day, which an agent should plan around. Beyond that it says nothing about authentication, pagination, result volume, whether the date is inclusive, or the return shape, leaving substantial gaps for a data-retrieval tool.

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 short sentences with the scope stated first and no filler. It is slightly telegraphic ('from a date') but nothing is wasted.

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 paginated-looking data-listing tool with no output schema and no annotations, the description should say more about what comes back (fields, count limits, ordering) and how the free tier behaves once exhausted. Those essentials are missing.

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?

At 50% schema description coverage, only 'lang' is documented in the schema; the description covers 'from' but mostly by repeating the YYYYMMDD format already encoded as pattern ^\d{8}$. It does not clarify whether the date is inclusive, how far forward results extend, or the ordering of returned events, so it only marginally compensates for the coverage gap.

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 (festivals and events in Korea) and a starting-point parameter, so an agent knows it is a listing tool for Korean festival data. It does not, however, distinguish itself from siblings such as kpop_new_concerts or request_korea_data, which could plausibly return overlapping event data.

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 statement of when to choose this tool over the other Korea-data siblings, nor any exclusions (e.g. 'only festivals, not concerts'). The '10 free calls/day' note constrains volume but is a quota, not usage guidance.

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