Get the artist profile including bio, images, social links, narrative voice, and AI presentation directives. Use this to introduce the artist to first-time listeners.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It lists what the tool returns but does not disclose any behavioral traits such as read-only safety, performance considerations, or side effects. The get verb implies non-destructive, but no explicit behavioral details are provided.
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 two sentences, front-loads the core purpose, and lists contents efficiently. Every word adds value, 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?
For a tool with no parameters, no annotations, and no output schema, the description sufficiently covers what the tool does and when to use it. The contents listed give a complete picture of the returned data.
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 tool has zero parameters, and the empty schema provides 100% coverage. Per rubric, zero params receive a baseline of 4; the description adds no parameter semantics because none are needed.
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 the artist profile and enumerates specific contents (bio, images, social links, narrative voice, AI presentation directives). This specific verb+resource combination distinguishes it from sibling tools like get_song and get_chapter.
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 explicitly says 'Use this to introduce the artist to first-time listeners,' providing clear context for when to use the tool. It does not mention exclusions or name alternative tools, but the usage guidance is sufficient for a simple getter.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action: artist profile, chapter details, curated experience playlist, experience presentation directives, individual song, chapter list, song list, and stream URL refresh. The only potential overlap is between get_song and list_songs with full=true, but descriptions clarify the use cases.
All tools follow a consistent verb_noun pattern (get_*, list_*, refresh_*) with snake_case, making it easy to predict tool names and understand their function.
8 tools is well within the ideal range for a read-only music catalog server. Each tool has a clear purpose and the set feels neither bloated nor sparse.
The tool surface covers the full user journey: discovering the artist, browsing chapters and songs, retrieving detailed song data, accessing curated experiences, and refreshing stream URLs. No obvious missing operations for a read-only API.
