ticketmaster_search_events

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the transparency burden. It adds valuable behavioral context by stating that a zero total with an empty events list is a valid no-results response, preventing misinterpretation. It also clarifies the accepted sort enum values, which is not covered by annotations.

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 short and mostly front-loaded, but the first sentence 'Search Ticketmaster events' is redundant with the second sentence, which already states the same action. Removing or merging the first sentence would make it tighter and more efficient.

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 3-parameter search tool with no output schema, the description is reasonably complete. It explains the no-results edge case and sort options, and the schema covers parameter details. It does not describe the full return structure, but the mention of an 'events list' gives enough context for basic use.

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 baseline is 3. The description adds meaningful value by explicitly listing the sort enum values (`relevance` and `date`), which the schema leaves unspecified. It also reinforces the `q` parameter semantics with different wording, though the schema already covers it adequately.

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 searches Ticketmaster events by artist, event, team, or venue, which is specific and actionable. This distinguishes it from sibling tools like ticketmaster_event or ticketmaster_discover_city_events, which focus on details or discovery rather than keyword 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 implies clear usage context: use this tool when you want to find Ticketmaster events via a text query. It does not explicitly mention alternatives or when not to use it, but the query types (artist, event, team, venue) provide enough guidance for an agent to decide when invocation is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.