top_artist_leaderboard

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

With no annotations provided, the description carries the burden. It does well: it discloses the quota (3× GET /me/top/artists) and reveals the fusion behavior of combining three windows into one ranking. It does not discuss side effects (none apparent) or error behavior, but for a read-only aggregation the key behavioral traits are covered.

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 sentences, both information-dense. The first sentence front-loads the core action and scoring weights; the second gives the quota. The only small waste is that the quota could be redundant with a debug-focused tool, but it is genuinely useful for API-cost planning.

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 aggregation with no required parameters and no output schema, the description conveys the algorithm, the API cost, and the input knobs. It lacks explicit ranking/response shape details, but the response_format enum covers that partially, and the lack of output schema lowers the burden.

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 schema already describes all three parameters with 100% coverage, so the baseline is 3. The description adds the notion of 'per window' interpretation for limit, which helps connect the parameter to the three-window behavior, but does not provide detail on how max_results or response_format interact with the scoring.

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 verb (Score), the resource (top artists), the scope (all three time windows), and the ranking scheme (recency-weighted points with multipliers). This distinguishes it clearly from siblings like get_top_artists, top_artists_by_range, and top_artist_ranking_delta without needing to open schemas.

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 formula and quota disclosure tell the agent what the tool does and what API cost it has, which implicitly covers when to use it. However, it does not explicitly state exclusions or name alternative tools for cases where this leaderboard is not needed, despite many similar siblings existing.

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