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

With no annotations, the description carries the full burden. It does disclose useful traits: no cost ('Free.'), a hard 6-month temporal window, any-language query support, and that the return is concert ids. It omits auth requirements, result limits/pagination, and what an agent must do with an id afterwards, which matters for a tool with zero annotation coverage.

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?

Three compact clauses with zero waste; cost, purpose, scope and return type are all front-loaded and skimmable. Nothing restates the schema or the name.

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 2-parameter, no-output-schema lookup tool this covers the essentials — what it searches, over what window, and that it returns ids. However, with no output schema the description is the only place to say how many ids come back or whether a follow-up call is needed, and it stays silent on both.

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%, so the schema already documents both q ('artist or title') and lang ('answer language: en/ja/ko'), setting the baseline at 3. The description's 'any language' adds a marginal nuance that queries may be issued in any language, but it does not explain the interaction between query language and the lang answer-language parameter.

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 (Search) plus resource (K-pop / pop concerts in Korea) and a precise scope (next 6 months, by artist or title). It clearly separates itself from a bare listing tool, but it never names or contrasts the obvious sibling kpop_new_concerts, leaving sibling differentiation to inference.

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 leading 'Free.' signal hints this is the no-cost option and 'by artist or title' implies a keyword-lookup use case, so usage is implied rather than stated. There is no explicit when-to-use vs kpop_new_concerts or korea_festivals, and no stated exclusions (e.g., what falls outside the 6-month window).

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