Get the loyalty/rewards program details for this site (Wix Loyalty). Returns program name, points currency name, and tier structure with required points per tier.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It clearly states the operation is read-only and lists the return content. However, it does not mention authentication requirements or potential errors (e.g., if loyalty program is not available).
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 a single sentence that is front-loaded with 'Get the loyalty/rewards program details'. It is concise with no wasted words, earning 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?
For a zero-parameter, no-output-schema tool, the description is reasonably complete. It specifies the returned fields. However, it could mention error handling or conditions (e.g., program existance).
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 tool has zero parameters, so the schema description coverage is 100%. The description adds no param-level info, as none exist. Baseline of 4 is appropriate since schema already tells all there is to know.
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 retrieves loyalty/rewards program details, naming specific return fields (program name, points currency, tier structure). This distinguishes it from other get_ tools like get_site_info which serves a different purpose.
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 provides no guidance on when to use this tool versus alternatives. There are no exclusions or context such as 'only if loyalty program is active' or 'use get_site_info for general site info'. The implicit hint 'for this site' is insufficient.
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.
All 28 tools have clearly distinct purposes. Overlaps like create_booking vs request_reservation are well-delineated by descriptions: one for appointments with checkout URL, the other for table requests via email confirmation. Similarly, reserve_event_tickets vs rsvp_event, and get_restaurant_menus vs search_dishes are complementary.
Tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_events, search_places). Verbs indicate action type (get/list for retrieval, create/reserve for creation), and nouns are specific entities. No mixing of conventions.
28 tools is above the typical 3-15 range but appropriate for the broad scope of a neighborhood directory with multiple Wix integrations (Bookings, Events, Stores, Reviews, etc.). Each tool covers a distinct feature, and no tool feels redundant.
The tool surface covers the main user workflows: searching places, viewing details and menus, checking availability, making bookings/reservations, and managing event tickets. Minor gaps exist (e.g., no update/cancel for bookings, no booking status check), but these are acceptable as the server focuses on initiating actions.