Search event weeks by name, description, or city. Use this to find specific conferences or festivals.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return | |
| query | Yes | Search query to match against name, description, or city |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries full burden for behavioral traits. It only states the search capability, omitting details like read-only nature, pagination (limit parameter implied but not explained), or error handling. No contradictory statements.
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 concise at two sentences, front-loading the core action. It wastes no words, though it could be slightly more structured with explicit parameter references.
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 (2 params, no output schema), the description is adequate for basic usage. However, it does not cover return format or selection criteria among siblings, which a more complete description would address.
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 coverage is 100% with descriptions for both query and limit. The description adds value by confirming that query matches name, description, or city, but does not add new semantics 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 clearly states it searches event weeks by name, description, or city, which is a specific verb-resource combination. It also mentions 'conferences or festivals' as examples, but does not explicitly differentiate from sibling tools like get_event_weeks.
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 suggests using the tool to find specific conferences or festivals, providing context. However, it lacks explicit when-not-to-use instructions or mention of alternative tools like get_event_weeks for listing all.
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.