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 behavioral burden. It clearly signals a read-only retrieval via 'Get' and discloses the exact return content (program name, points currency, tier structure). It doesn't mention auth or side effects, but a zero-parameter getter has minimal behavioral complexity.
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, front-loaded sentence that states the action, resource, and important return fields. It contains no filler and each phrase adds useful 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?
For a no-input, no-output-schema tool, the description fully covers what is returned and scopes to the current site. It is complete and leaves no major gaps for an agent to invoke and interpret correctly.
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 and an empty input schema, so the baseline of 4 applies. No parameter explanation is needed, and the description focuses on what the returned data contains.
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 uses a specific verb ('Get') with a concrete resource ('loyalty/rewards program details') and scopes it explicitly to 'this site (Wix Loyalty)'. It clearly distinguishes itself from sibling tools like get_site_info by naming the loyalty domain and the exact return fields.
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 clear context: use this tool to retrieve the Wix Loyalty program details for the current site. It doesn't explicitly list exclusions or alternatives, but the scope and output are specific enough that the intended use case is unambiguous.
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 resource or action: booking services, restaurant reservations, event tickets, and RSVPs are all clearly separated by domain and described with explicit use cases. Similarly, search_places, search_dishes, and get_restaurant_menus cover different granularities of place/menu lookup. The descriptions include guidance on when to use each tool, eliminating ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_*, get_*, create_*, search_*). While a few verbs like 'request' and 'rsvp' differ, they accurately reflect the action's semantics and do not break the overall consistency. The naming makes the tool's purpose predictable from its name.
At 28 tools, this is a large set, but it serves a broad multi-domain directory (places, events, movies, store, bookings, content, etc.). Each tool covers a distinct feature or resource, and there are no redundant tools. The count is at the upper boundary but appropriate for the server's comprehensive scope.
The tool surface covers the full lifecycle for the directory's main domains: search/discover places, view details, menus, reviews, book services, reserve/RSVP events, browse movies/showtimes, list products, access content (blog, guides, FAQs), submit forms, and check loyalty. There are no obvious dead ends or missing operations for the stated purpose. The inclusion of pairing tools like list_forms→submit_form and get_availability→create_booking shows deliberate workflow completeness.