get_artist_top_albums

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, establishing this as a safe read operation. The description adds behavioral context about pagination (limit/page) and autocorrect functionality, which are not covered by annotations. It does not contradict the annotations and provides useful extra detail.

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 structured Args list. It is front-loaded with the main purpose and provides parameter details efficiently without any fluff or redundancy. Every sentence 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 list tool, the description covers the purpose, all parameters, and pagination behavior. It does not describe the response format, but an output schema exists to handle that. It lacks explicit mention of sorting or rate limits, but these are not critical for a simple retrieval operation. The description is sufficiently complete for an agent to call it correctly.

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?

The schema has zero property descriptions (coverage 0%), so the description must compensate. It fully explains each parameter: artist (required unless mbid given), mbid (MusicBrainz ID), limit (results per page), page (which page to fetch), and autocorrect (fix misspelled names). This adds meaningful semantics beyond the raw schema and clarifies the relationship between artist and mbid.

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 states 'Get an artist's most played albums.' This clearly identifies the action (get) and the specific resource (artist's most played albums). It distinguishes itself from sibling tools like get_user_top_albums and get_tag_top_albums by targeting the artist context. It is a precise, non-tautological statement.

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 does not provide any guidance on when to use this tool versus alternatives. It does not mention alternatives, prerequisites, or exclusions. The only usage hint is that 'artist' is required unless 'mbid' is given, which is more about parameter selection than tool selection. There is no comparison to get_artist_top_tracks or other artist-specific tools.

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