get_artist_top_tracks

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully reveals the ~10 track cap and the absence of a full-catalog endpoint, which are meaningful constraints. It does not mention auth, error behavior, or other side effects, but the tool is a simple read operation and output schema exists.

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 one tight, front-loaded sentence with the core action stated first. The parenthetical is useful context about the tool's limits, not filler, so every part 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?

For a one-parameter lookup with an output schema, the description is mostly adequate and the cap note is valuable. However, it omits usage context such as how top tracks relate to the other track/album endpoints and provides no parameter guidance, leaving some gaps for the agent to infer.

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%, and the description adds no information about the artist_id parameter beyond the name already present in the schema. It does not specify whether this is a Spotify ID, URI, or URL, so it fails to compensate for the low schema coverage.

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 clearly identifies the operation: 'Get an artist's top tracks,' naming a specific resource and action. It does not explicitly distinguish this from sibling tools like get_artist_albums or get_album_tracks, so it stops short of a 5.

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?

There is no guidance about when to choose this tool over the many sibling track/album tools, nor any when-not-to-use note. The parenthetical explains a platform limitation but does not route the agent to an alternative or state selection criteria.

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