List upcoming conference weeks, festivals, and multi-day event series (like ETH Denver, Devconnect, Token2049). Use this to help users plan trips around major conferences.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Filter by tag (e.g., 'crypto', 'music', 'tech') | |
| city | No | Filter by city name | |
| limit | No | Maximum number of event weeks to return | |
| country | No | Filter by country name | |
| include_past | No | Include past event weeks (default false) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description says it lists 'upcoming' events, implying a time filter, but does not explain default behavior (e.g., include_past param) or response format. No annotations are provided, so the description bears the burden but gives only basic behavior.
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 concise sentences with no waste. The purpose and a sample use case are presented clearly and 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?
Given 5 parameters and no output schema, the description could explain return structure or defaults. However, the tool seems intended for listing summaries, and companion tools (get_event_week_details) exist for details. It adequately covers the core use case.
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%, so the description does not need to add parameter details. The description does not mention any parameters, which is acceptable given full schema documentation.
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 lists upcoming conference weeks, festivals, and multi-day event series, with specific examples (ETH Denver, Devconnect, Token2049). It distinguishes from siblings like search_event_weeks by using 'list' rather than 'search'.
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 provides a usage hint: 'Use this to help users plan trips around major conferences.' However, it does not specify when not to use it or contrast with alternatives like search_event_weeks.
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.