Create a direct checkout URL for one or more store products (Wix Stores). The user clicks the URL to complete payment on the site — no login required on the AI agent side.
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Products to add to cart. |
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 discloses key behavioral aspects: no login required for the agent, and the user completes payment by clicking the URL. This adds context beyond the schema, though it doesn't cover all potential side effects or response details.
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 two sentences, front-loaded with the main action and a clarifying detail about authentication. No filler or redundancy.
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 simple tool with one parameter and no output schema, the description explains the core purpose and auth requirement. It doesn't explicitly state the return format, but the phrase 'checkout URL' implies a URL response, so it is reasonably complete.
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 description coverage is 100%, with 'items' described as 'Products to add to cart' and productId referenced as from list_products. The tool description adds minimal extra parameter context beyond the schema, so the baseline 3 is appropriate.
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?
Description clearly states the tool creates a direct checkout URL for one or more store products, using a specific verb and resource. It distinguishes from sibling tools like create_booking by mentioning Wix Stores and the payment flow.
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?
Implied usage context: the agent should use this to generate checkout links for products obtained via list_products. However, it doesn't explicitly say when not to use it or mention alternatives, so guidance is largely implicit.
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 (e.g., create_booking vs create_checkout, reserve_event_tickets vs rsvp_event), and descriptions provide clear boundaries. Even closely related tools like list_booking_services and list_pricing_plans are differentiated by context.
All 26 tools follow a consistent snake_case verb_noun pattern (get_, list_, create_, search_, etc.), with no mixed conventions or vague verbs. This makes the tool set predictable and easy to navigate.
At 26 tools, the set is on the heavy side and exceeds the typical well-scoped range, but the diversity reflects a multi-featured directory covering bookings, events, store, reviews, forms, and more. Each tool appears to serve a distinct purpose, so the count is borderline rather than excessive.
The surface covers the core user workflows: search, view details, book services, reserve/RSVP events, request reservations, submit forms, and browse content. Minor gaps exist (e.g., no cancellation/update for bookings, no full blog post body), but these are workarounds and not critical for a consumer-facing directory.
