get_artist

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

With no annotations provided, the description must disclose all behavioral traits. It only says 'get detailed info,' implying a read operation, but it does not mention authentication requirements, rate limits, data freshness, or whether the bio is returned in the specified language.

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?

A single sentence that aptly summarizes the tool's purpose. Every word is necessary; no fluff. The key components are front-loaded.

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 lists the main data types (bio, stats, tags, similar artists) but does not specify the return format or structure. Given the lack of an output schema and many sibling tools, more detail about the response would improve completeness. Adequate for a simple fetch, but gaps exist.

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 schema describes all parameters. The description adds high-level context (bio, stats, tags, similar artists) but does not explain how parameters like 'lang' or 'autocorrect' interact with the output. Baseline of 3 is appropriate.

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 tool retrieves detailed artist info including bio, stats, tags, and similar artists. It distinguishes from sibling tools that focus on specific aspects (e.g., get_artist_top_albums). However, it does not explicitly differentiate itself from get_artist_top_tags or get_similar_artists, which are listed as siblings.

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?

No guidance on when to use this tool versus its many siblings (e.g., get_artist_top_albums for top albums only). The description does not specify prerequisites or whether it replaces other tools like get_similar_artists. This leaves ambiguity for an AI agent.

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