Get ticket types and prices for a specific event (Wix Events). Pass the event slug from list_events. Returns ticket names, prices, sale status, and how many are left.
| Name | Required | Description | Default |
|---|---|---|---|
| event_slug | Yes | Event slug from list_events. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It describes the tool as retrieving ticket information (names, prices, sale status, how many left), implying a read-only operation. However, it doesn't explicitly state read-only or mention auth requirements or rate limits. The output description adds transparency.
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, both informative and front-loaded. The first sentence states purpose and context, the second gives input and output. No unnecessary words.
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?
Despite no output schema, the description summarizes what is returned. It fits well with sibling tools: list_events provides slugs, get_event_tickets provides details, reserve_event_tickets takes action. The description is sufficient for an agent to understand how to use the tool in context.
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?
The schema describes event_slug with 'Event slug from list_events.' The description reinforces this and explains where to obtain the slug, adding context beyond the schema. With 100% schema coverage, the baseline is 3, but the description adds value by clarifying the source.
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 verb 'Get', the resource 'ticket types and prices', and the context 'Wix Events'. It specifies the input (event slug from list_events) and output (ticket names, prices, sale status, amount left). This differentiates it from sibling tools like reserve_event_tickets and rsvp_event.
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 explicitly instructs to pass the event slug from list_events, providing a clear dependency. It implies usage before reserving tickets, but does not explicitly state when not to use it or mention alternatives. The guidance is helpful but not exhaustive.
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.
Each tool targets a distinct operation: bookings, restaurants, events, forms, etc. Even similar actions like create_booking and request_reservation are clearly differentiated by domain and description.
Tools follow a consistent verb_noun pattern (e.g., create_booking, get_availability, list_blog_posts). Collection retrieval uses list_ while single item uses get_, which is a standard and clear convention.
28 tools is on the upper end, but each serves a distinct function for a comprehensive neighborhood directory (places, events, booking, forms, etc.). No obvious bloat given the scope.
The tool surface covers all major user intents for a local directory: searching places, getting menus, booking services, viewing events, submitting forms, etc. No critical gaps are apparent.