get_venue_infoAddress, contact details and the venue's FAQ (house rules, practical questions). Use this to answer buyer questions about the club instead of guessing.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Language for titles, labels and the returned URLs. Defaults to fr. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already communicates that this is a safe read operation. The description adds useful content context—what kind of venue information is returned (address, contact, house rules, practical questions)—but does not reveal additional behavior such as localization defaults or response shape, which is acceptable given the annotation coverage.
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 fluff. The first sentence front-loads the core content, and the second adds a practical usage directive. Every word earns its place.
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?
With a single optional parameter fully described in the schema, an output schema present, and readOnlyHint set, the description provides everything an agent needs to select and call it correctly. Nothing essential is missing.
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 input schema fully documents the only parameter (locale), including its allowed values and default. The description adds no parameter-specific detail, but none is needed because schema coverage is 100%.
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 identifies the resource—address, contact details, and FAQ—and the name 'get_venue_info' supplies the retrieval verb. It distinguishes from sibling tools like get_availability or get_booking_status by focusing on venue facts, though it doesn't explicitly contrast itself with those 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?
It explicitly instructs when to use this tool: 'Use this to answer buyer questions about the club instead of guessing.' This gives a clear use case, but it does not mention exclusions or name alternative tools for situations where venue info is not the answer.
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 steps in the booking lifecycle, but get_booking_status and wait_for_payment serve nearly the same purpose, and get_event/list_events/get_availability all surface availability. Descriptions are strong enough to prevent frequent misselection.
All tools use a consistent verb_noun snake_case pattern (get_*, hold_tickets, redeem_*, release_booking, set_contact, wait_for_payment). There are no style or naming convention breaks.
Twelve tools map cleanly to the ticket-buying workflow: discovery, venue info, availability, hold, contact, payment, redemption, release, status, and recovery. Each tool earns its place without redundant bulk.
The lifecycle is well covered: hold, contact, payment, redemption, release, and post-sale recovery are all present. The only notable gap is lack of any cancellation/refund path for paid bookings, though this may be intentional venue policy.