ticketmaster_venue_events

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

No annotations are provided, so the description carries the full burden. It only restates the core function ('Returns upcoming Ticketmaster events at one venue') and adds the sort enum values. It does not disclose pagination behavior, whether events are sorted by date by default, timezone implications, or any other behavioral nuance.

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 but somewhat redundant—'List a venue's Ticketmaster events' and 'Returns upcoming Ticketmaster events at one venue' say nearly the same thing. It is not as polished as it could be, though it does front-load the key 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?

The tool is simple and has no output schema, but the description does not mention what fields the returned events contain or how many results are returned. It gives the essential 'what' but lacks enough detail for full context, though it is adequate for a straightforward listing tool.

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%, but the description adds valuable detail by explicitly listing the accepted sort values (`relevance` and `date`), which the schema does not provide. This goes beyond the baseline and assists with correct parameter usage.

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 action ('List'), the specific resource ('a venue's Ticketmaster events'), and the scope ('upcoming', 'at one venue'). This differentiates it from sibling tools like ticketmaster_search_events or ticketmaster_attraction_events, which cover different scopes.

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?

Clear context is provided: this is for a single venue's upcoming events, requiring a venue ID. However, it does not explicitly mention exclusions or alternatives (e.g., when to use ticketmaster_search_events instead), so it falls short of a full 5.

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