get_artist_top_tracks

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

Since there are no annotations, the description carries the full burden of behavioral disclosure. It clearly discloses the tool's removal and unavailability for newer app registrations, which is a significant behavioral trait that could prevent failed calls. It does not cover other behaviors like rate limits or auth, but for a tool that is effectively deprecated, this disclosure is valuable.

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 concise, with the core purpose stated first and the deprecation warning appended. It is efficient and easy to parse, though it could have been slightly clearer about the parameter mismatch. No wasted words.

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 tool that is removed, the description provides the essential warning and basic purpose. However, it lacks details on the return format or how the 'ten most-played' relates to the max_results parameter. Given that the tool is deprecated, this may be sufficient, but it is not fully complete for an agent that might need to understand its behavior before calling.

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 coverage is 100%, so parameters are documented, but the description introduces an inconsistency: it says 'ten most-played tracks' while the schema's max_results parameter defaults to 50 and allows up to 2000. This could mislead an agent into thinking the tool returns exactly ten tracks by default, contradicting the schema. The description adds confusion rather than clarity beyond the schema.

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 ('Get'), a specific resource ('an artist's ten most-played tracks'), and a scope ('for a market'). It clearly conveys what the tool does, and the mention of 'ten most-played tracks' distinguishes it from other artist-related tools like get_artist_singles or get_artist_albums, even though it doesn't name alternatives.

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 does not provide explicit when-to-use guidance or name alternative tools, but it includes a critical constraint: 'Removed by Spotify's February 2026 Web API changes — unavailable for newer app registrations.' This implicitly tells agents to avoid using it for newer app registrations, but it does not suggest what to use instead. That is partial usage guidance.

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