get_artist_albums

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

No annotations provided, so the description fully bears the burden. It explains input constraints (artist_id required, optional include_groups with allowed values, limit with max=50), return structure with fields, and error handling ('error' field). No contradictions or omissions.

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 long but well-organized with sections 'Arguments' and 'Returns'. While every sentence adds value, some redundancy (e.g., repeating 'album' types) could be trimmed. Still reasonably concise for the detail provided.

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?

The description is fully self-contained: it explains input, output (including nested structures like artist and album objects), optional parameters, defaults, and error handling. Given 3 params and a complex return type, it addresses all necessary information. The output schema is described in detail, so no gaps remain.

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% (no descriptions on schema props), but the description thoroughly explains each parameter: artist_id (Spotify ID), include_groups (allowed values and default), and limit (default 20, max 50). This adds critical meaning beyond schema names and types.

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 opens with 'Get albums for an artist', a specific verb-resource pair. It distinctly differs from sibling tools like get_artist (artist info), get_artist_top_tracks (top tracks), and search_artists (search). The return type and parameters reinforce the clear purpose.

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 usage: provide an artist_id and optionally filter by album type or limit results. However, it does not explicitly state when to use this over alternatives like get_artist_top_tracks (for top songs) or get_new_releases (for new albums). A brief note on when not to use it would improve clarity.

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