List artist top tracks

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the pagination behaviour ('page through'), which is genuinely useful context, but says nothing about ranking basis, region/catalog dependence, or empty-result behaviour.

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?

A single short, front-loaded sentence with no wasted wording. It is efficient, though the terseness is close to under-specification rather than deliberate concision.

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?

An output schema exists, so return values need not be described, and the schema covers limit/offset bounds. However, for a required-param, paginated list tool the definition omits what 'top' is ranked by and how the required artist_id is obtained, leaving gaps an agent must guess at.

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 0% for three parameters. 'Page through' gestures at limit/offset semantics but gives no default/bound context beyond what the schema already declares, and the required artist_id parameter is completely unaddressed (format, source, length constraints).

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 identifies the resource ('an artist's most prominent tracks') and implies a list/read operation, but 'most prominent' is a loose paraphrase of the tool name's 'top tracks' and the phrase 'page through' is vague about what is actually returned. It does not differentiate this from siblings like tidal_get_artist_radio, tidal_get_artist_albums, or tidal_get_artist_videos.

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 only usage hint is the word 'page through', which suggests browsing rather than a one-shot fetch, but there is no statement of when to choose this over tidal_get_artist_radio, tidal_get_artist_similar, or the general search tools. No prerequisites (artist_id must resolve) are mentioned.

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