itunes_get_artist_top_tracks

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

No annotations are provided, so the description carries the transparency burden. It clarifies that the search is against the global catalog and that results are top tracks with a configurable limit (default 10, max 25), but it does not disclose result format, error behavior, or authentication/rate-limit expectations.

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 a single clear sentence followed by a compact two-item Args list. Every phrase adds useful information and is front-loaded with the main action.

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 simple two-parameter read/search tool, the description is nearly complete: it states the catalog scope, result type, and parameter constraints. It only lacks explicit mention of the return value shape, which would be helpful given there is no output schema.

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 0%, but the description fully compensates by explaining 'artist' as the name to search and 'limit' as the number of top tracks to return, including the default and max 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?

Description uses a specific verb ('Search') with a clear resource ('Apple Music's global catalog') and output ('top tracks by any artist'). This distinguishes it from siblings like itunes_get_artist_albums and itunes_get_top_charts.

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 it should be used when the caller wants top tracks for a named artist, but it does not explicitly mention alternatives or when not to use it. With many sibling search/artist tools, an explicit pointer to e.g. itunes_search_catalog or itunes_get_artist_albums would strengthen this.

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