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 the full burden. It states the tool lists products and returns specific fields, but does not disclose any side effects, authentication requirements, rate limits, or explicitly confirm it is read-only. This lack of behavioral context is a significant gap for a mutation-free tool, though 'list' implies read-only.
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 tool's purpose and output fields. It is concise with no fluff, earning a 5.
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 no output schema, the description should explain the return values. It lists the fields but does not specify the structure (e.g., array of product objects) or any additional behavior such as pagination defaults or ordering. For a simple list tool, this is adequate but incomplete, scoring a 3.
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 has full description coverage for both parameters (q and limit). The description adds no additional parameter context beyond what the schema already provides, so 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?
The description clearly states it lists products in the site's Wix Stores, with a specific verb and resource. It also mentions the return fields, which matches the tool's purpose. It distinguishes from sibling list tools by targeting products specifically.
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 implies usage when product information is needed but provides no explicit guidance on when to use this tool versus alternatives. There are no exclusions or comparisons to other list_* tools, so the agent must infer from the resource name.
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.