List cities that have events, with statistics like total events and recent activity. Use this to help users discover active event scenes.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of cities to return | |
| country | No | Filter by country name | |
| min_events | No | Minimum number of total events |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It hints at output contents ('statistics like total events and recent activity') but does not disclose behavioral details such as read-only nature, error handling, rate limits, or ordering. Some transparency but significant gaps.
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, front-loaded with the core purpose. No unnecessary words; every sentence adds value.
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 has 3 parameters, no output schema, and no annotations, the description provides a high-level purpose but lacks details on what 'statistics' specifically include, how parameters affect output, or ordering. Adequate but not fully complete for an agent to use optimally.
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 parameter descriptions already provided. The tool description adds no additional meaning to the parameters (limit, country, min_events), so it does not improve upon 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?
Description clearly states the tool lists cities with events and includes statistics like total events and recent activity. It distinguishes from sibling tools by focusing on cities rather than specific events or venues, though it does not explicitly contrast with siblings.
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?
Description provides a use case ('help users discover active event scenes') but does not specify when to use this tool over alternatives like search_events or get_venues. No exclusions or context for selection are given.
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.