top_artist_ranking_delta

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

With no annotations, the description carries the behavioral burden and does meaningful work: it discloses output ordering ('climbers first'), the default comparison windows, and the quota cost ('2× GET /me/top/artists'). It does not mention response shape or edge cases, but the core behavioral traits are surfaced.

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 deliver the core behavior, ordering, defaults, and quota with no filler. The most important information is front-loaded and every clause earns its place.

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?

The description is sufficient for a simple comparison tool: it covers what is computed, the default windows, ordering, and quota. Since there is no output schema, a bit more detail about the exact returned structure would help, but the response_format parameter partially covers output expectations.

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 input schema already documents all four parameters with defaults, enums, and descriptions, so schema coverage is 100%. The description adds context about the default comparison direction and ordering, but does not need to repeat parameter details.

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 uses a specific verb ('Show') and resource ('each top artist's rank moved'), plus the key comparison between two time windows. It clearly distinguishes this tool from static ranking tools like top_artist_leaderboard and from the track-level sibling top_track_ranking_delta.

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 tool is for rank-movement analysis between time windows and states the default comparison, but it does not explicitly say when to choose this over siblings or when to avoid it. No alternative tools are named, leaving usage guidance to inference.

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