List products in this site's store (Wix Stores). Returns name, price, stock status, and product type.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Optional search term matched against product name. | |
| limit | No | Max products to return (default 20, max 100). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full behavioral burden. It discloses that the tool lists products and returns specific fields, which is useful. However, it does not mention authorization requirements, side effects, or whether the store must exist, leaving some gaps for a tool with no annotation safety net.
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 efficiently conveys the tool's purpose and output. Every word serves a purpose, with no extraneous 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?
Given the tool's simplicity (2 optional params, no output schema), the description adequately covers what the tool does and what it returns. The mention of 'Wix Stores' provides useful context. It could optionally mention pagination or sorting, but it is complete enough for most use cases.
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 coverage is 100%, with both parameters (q, limit) already described clearly in the input schema. The description adds no additional parameter semantics beyond what the schema provides, so the baseline score of 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?
The description clearly states it lists products in the site's store (Wix Stores) and specifies the returned fields (name, price, stock status, product type). The verb 'List' and resource 'products' are specific, and the mention of 'Wix Stores' distinguishes it from other listing tools for different resource types.
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 does not provide explicit guidance on when to use this tool vs alternatives like list_blog_posts or list_categories. However, the tool name and the 'Wix Stores' context imply it is for store products, making usage clear but not explicitly differentiated.
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.