get_festivalDetails for one festival: dates, location, venue, genres, description, ticket availability and links. Accepts a festival name, Setline id, or URL slug.
| Name | Required | Description | Default |
|---|---|---|---|
| festival | Yes | Festival name, Setline id, or URL slug (e.g. "rock-am-ring-2026"). |
| Name | Required | Description | Default |
|---|---|---|---|
| app | No | ||
| hint | No | ||
| error | No | ||
| query | No | ||
| source | Yes | ||
| festival | No | ||
| didYouMean | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds scope ('one festival') and returned content, but does not discuss error behavior or handling of ambiguous names, which is acceptable but not rich.
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 with no filler; the core purpose and field list are front-loaded, and the accepted input forms are stated compactly. Every sentence contributes necessary information.
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 one-parameter, read-only lookup with annotations and an output schema, the description is largely sufficient. It clearly defines input forms and returned content. Minor gaps remain around when to use search_festivals instead and behavior on ambiguous matches, preventing a 5.
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 input schema covers the single parameter 100%, including the accepted forms and an example. The description's second sentence repeats this information without adding additional semantic detail, so the baseline of 3 applies.
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?
States a specific retrieval action for one festival and enumerates the returned fields (dates, location, venue, genres, description, ticket availability, links). The 'one festival' scope distinguishes it from sibling search tools.
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?
Usage context is implied: call when you have a festival name, Setline id, or URL slug. However, it does not explicitly mention when to prefer search_festivals or other alternatives, so the guidance is not fully explicit.
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.