Get one artist's profile with their upcoming dates and recent history. Provide artist_id, slug, or name. Use this to answer 'Tell me about Tale of Us' or 'What is Objekt up to?'
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Exact artist name | |
| slug | No | Artist slug, as used by /artist/:slug | |
| artist_id | No | Artist UUID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool returns a profile, upcoming dates, and recent history, plus the acceptable identifier types. However, it doesn't mention any auth requirements or potential limitations, but for a read-only profile fetch, this is adequate.
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-loaded with the action and resource, and includes practical examples. No wasted words.
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's simplicity and 100% schema coverage, the description sufficiently explains the return content and usage context. It could mention the output structure, but the absence of an output schema is mitigated by the clear description of what is returned.
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 descriptions cover all three parameters, so the baseline is 3. The description adds value by clarifying that artist_id, slug, or name are alternative ways to specify the artist, which is not explicitly stated in the schema. This helps the agent know any one can be provided.
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 specifies 'Get one artist's profile with their upcoming dates and recent history,' which clearly distinguishes it from sibling tools like get_artist_events or search_artists. Examples of natural language queries reinforce the 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?
It states when to use it via examples ('Use this to answer...'), but does not explicitly mention when not to use or point to alternatives like get_artist_events for event-only queries. Still, the context is clear.
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.
Most tools target distinct resources and actions, such as get_artist vs get_artist_events and get_event_schedule vs get_now_playing. A few pairs like list_artists/search_artists and get_event_weeks/search_event_weeks could be confused, but their descriptions clarify browse vs search.
Tool names follow a consistent verb_noun pattern with get, list, and search. Minor inconsistency exists because get_ is used for both singular retrieval (get_artist) and collection listing (get_cities, get_event_weeks), while list_ only appears in list_artists. Overall predictable and readable.
16 tools is slightly above the typical 15-tool threshold but well-justified by the broad domain covering artists, events, venues, cities, event weeks, and organizers. Each tool serves a distinct purpose and none feel redundant.
The surface is comprehensive for a read-only events data API, covering artist browsing/search/details, event search/details/schedule/live, venue listing, city stats, event week management, and organizer search. Minor gaps include absent get_venue_details and get_organizer, but these can be derived from event details.