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

With no annotations, the description carries the burden. It discloses that the data sources are external to KTRENZ and explains the velocity metric's components, but it omits any mention of output format, pagination, rate limits, or potential edge cases. This is adequate for a simple read operation but not rich.

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 concise sentences with the core purpose front-loaded. It defines velocity, lists its components, and emphasizes that rank is the signal, all without wasted words. The structure is efficient and easy to parse.

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 simple tool with one optional parameter and no output schema, the description covers the main purpose and ranking logic. However, it does not specify the output structure or any details about the returned artist objects, leaving some ambiguity for an agent about what fields to expect.

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?

The only parameter, limit, is fully documented in the schema with range and default, so schema coverage is 100%. The description adds no extra meaning about the parameter beyond what the schema already provides, so a baseline of 3 is appropriate.

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 clearly states the tool returns top rising K-pop artists ranked by 7-day velocity, explicitly contrasting with standing popularity. It distinguishes itself from siblings by focusing on velocity rather than reach or search, making its purpose unmistakable.

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 implies usage for trending/velocity data and explicitly says 'not standing popularity', which hints at when not to use it, but it does not name alternative tools or provide explicit when-to-use conditions. The contrast is helpful but underdeveloped.

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