search_artistsSearch artists who are playing upcoming festivals. Returns each artist with their upcoming festival appearances.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results, 1-25. Default 10. | |
| query | Yes | Artist name or part of it. |
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | ||
| source | Yes | ||
| artists | Yes | ||
| totalMatches | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already convey readOnly, non-destructive, and idempotent behavior. The description adds useful behavioral context by saying results are limited to artists with upcoming festival appearances and that each result includes festival appearances, but it does not describe edge cases such as empty results or match behavior. This meets the baseline but does not go beyond it significantly.
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 concise sentences: one states the search scope, the other states the output. There is no fluff or repetition, and the most important action is 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?
For a simple, read-only search tool with full schema descriptions, annotations, and an output schema, the description is essentially complete. It lacks only an explicit pointer to sibling tools for different lookup needs, but that gap is minor given the simplicity and clear scope.
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 query and limit are already documented in the schema. The description reinforces that the search is for upcoming-festival artists but adds no additional parameter-level meaning beyond the schema.
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 uses a specific verb ('Search') and resource ('artists') and adds a clear scope qualifier: artists playing upcoming festivals. It also states the output shape, distinguishing it from single-entity tools like get_artist and from search_festivals.
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 clearly implies this tool is for searching artists by name, specifically those with upcoming festival appearances. It does not explicitly name alternatives or state when not to use it, but the scope and output make the intended use case understandable.
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 or query type: artist details, festival details, lineups, set times, and searches. The only potential confusion is between search_festivals and whats_on, since both can find festivals by date, though their descriptions clarify the different default uses.
Most tools follow a clear get_/search_ verb_noun pattern (e.g., get_artist, search_festivals). The outlier is whats_on, which breaks the pattern and uses a phrase without an underscore, but it is still understandable and not disruptive.
Seven tools is well-scoped for a festival and artist information server. Each tool covers a meaningful aspect of the domain without redundancy or bloat.
The surface covers the core domain well: finding artists and festivals, retrieving festival details, lineups, and schedules, plus a what's-on-view. As a read-only information service, create/update/delete operations are not expected, and there are no obvious dead ends.