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

With no annotations provided, the description carries the burden of disclosing behavior. It notes provenance ('Measured first-party by KTRENZ') and the data dimensions, but it does not explicitly state read-only behavior, absence of side effects, rate limits, or caching. There is no contradiction, but behavioral transparency is thin.

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 description is two sentences and every clause adds information: the reach dimensions, momentum window, and data source. It is appropriately front-loaded with the core purpose. Some jargon ('answer-time vs training', '7d momentum') is dense but not wasteful, so it remains efficient.

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 one-parameter read tool with no output schema, the description lists the main result categories and the momentum window, which is enough to understand what the tool returns at a high level. It does not define the jargon or specify return format, but for a simple slug-based lookup it is reasonably 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%: the slug parameter is fully described with type, source (search_kdata), and an example. The description adds no parameter-specific meaning beyond the schema, so the baseline of 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 names the exact resource (artist reach) and enumerates its measured components: AI answer engines with vendor citations and answer-time vs training, tracked releases, and external demand from Naver and YouTube. This clearly distinguishes it from sibling get_release_reach by being artist-level, and the title 'Artist reach map' reinforces the resource.

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 provides no explicit guidance on when to use this tool versus get_release_reach or get_trending, and it does not state any exclusions. The only usage hint is in the schema parameter description pointing to search_kdata for finding the slug, but the main description itself offers no decision guidance.

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