playlist_artist_heat

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

No annotations are provided, so the description carries the behavioral burden. It signals read-only behavior via the quota hint ('🟢 1 GET') and clearly enumerates the computed metrics. However, it does not disclose details like whether the analysis follows only top-level tracks, how HHI is calculated, or any pagination/limits behavior beyond the quota.

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 sentences with a clear label, a concrete output list, and an emoji flag for quota. Every sentence earns its place: what the tool produces, the business question it answers, and the cost hint. No filler or redundancy.

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 read-only analysis tool with full schema parameter coverage and no output schema, the description defines the metrics well. The remaining gaps are minor: it does not define the HHI scale or the exact criteria for the 'repeat-offender' list, and it does not explicitly state the default behavior for large playlists. Overall, it is sufficiently complete for an agent to call it correctly.

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 all five parameters well. The description adds context about the overall output metrics but does not explain how top_n, max_results, or response_format affect the returned concentration metrics. Baseline 3 is appropriate because the schema carries the documentation load.

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 states a specific verb and resource ('Local artist-concentration check'), lists three concrete outputs (top-artist share, HHI concentration index, repeat-offender list with track counts), and includes a plain-language question ('Is this mix just one band?'). This clearly differentiates it from the many sibling tools.

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 the use case: analyzing whether a single artist dominates a playlist. The example question and the 'local artist-concentration check' provide clear context for when to use it. However, it does not explicitly name alternative tools or state when not to use it, so it stops short of full routing guidance.

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