get_artist_details

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it's a read operation (implied by 'Get'), specifies what data is returned, and importantly reveals the limitation of showing 'first 10 release groups' rather than all. It doesn't mention rate limits, authentication needs, or error conditions, but provides substantial operational context.

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, zero waste. First sentence delivers core functionality with specific data points. Second sentence provides crucial usage guidance and sibling differentiation. Every word earns its place with no redundancy or fluff.

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?

Given the tool has an output schema (so return values are documented elsewhere), no annotations, and simple single-parameter input, the description is complete. It covers purpose, data returned, limitations, and sibling differentiation - exactly what's needed for an agent to understand when and how to use this tool effectively.

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?

With 0% schema description coverage and only one parameter, the description doesn't explicitly mention the 'artist_id' parameter. However, it strongly implies the need for artist identification through context ('about an artist'), and the tool's purpose is clear enough that the parameter's role is reasonably inferable. For a single-parameter tool, this is acceptable.

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 specific action ('Get comprehensive info') and resource ('about an artist'), listing the exact data included (aliases, tags, genres, discography with MBIDs). It explicitly distinguishes from sibling 'get_artist_discography' by noting this tool shows only first 10 release groups versus the full paged list.

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?

Explicit guidance is provided on when to use this tool versus alternatives: 'use get_artist_discography for the full paged list' directly names the sibling tool for extended discography needs. This creates clear boundaries between tools for different use cases.

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