get_artist_top_tracks

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

No annotations are provided, so the description bears full responsibility. It does disclose the February 2026 removal and unavailability for newer apps, which is useful. However, it says 'ten most-played tracks' while the schema default is 50 and max is 2000, creating an inconsistency. It also doesn't mention errors, rate limits, or what happens when the endpoint is unavailable.

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 with no filler. The purpose is front-loaded and the deprecation warning is placed second, which is a logical order. Every word 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 read-only fetch tool with no output schema, more guidance is needed. The deprecation is mentioned but not the workaround or alternative endpoints. The mismatch between 'ten' and the configurable max_results leaves the agent uncertain about actual behavior. A tool that may be broken in many environments needs more context than this.

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 100%, so the baseline is 3. The description does not add parameter-level detail beyond the schema, and the 'ten' wording could confuse interpretation of max_results. No severe gap, but no added value either.

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 states the action and resource: 'Get an artist's ten most-played tracks for a market.' It is distinct from sibling tools like get_artist or get_top_tracks (which likely refer to the user's own top tracks). The 'ten' is somewhat inconsistent with the max_results parameter, but the core purpose is unambiguous.

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 deprecation note tells the agent when the tool is unavailable ('newer app registrations') but offers no alternative tool to use instead. There is no guidance on choosing this over sibling tools like get_artist_top_tracks or get_artist. The when-not-to-use is only partially addressed.

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