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 must fully convey behavioral traits. It states the tool lists products and returns specific fields, implying a read-only operation. However, it fails to mention pagination behavior (though 'limit' is in schema), ordering, or any side effects. The description is functional but lacks depth expected for an unannotated tool.
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, clear sentence with no filler. It front-loads the key action (List products) and efficiently communicates the return fields. No unnecessary information is present.
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 is a simple list with no output schema and no annotations, the description covers the basic purpose and return fields. However, it does not mention pagination details (beyond the limit parameter in the schema) or any ordering, which would enhance completeness for an agent. Still, it is mostly adequate.
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%, so the baseline is 3. The description does not add any additional meaning to the parameters beyond what the schema already provides (q and limit are clearly described in the schema). No extra value is contributed by the description for parameter understanding.
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 verb 'List' and the resource 'products in this site's store (Wix Stores)', and specifies the returned fields (name, price, stock status, product type). This distinctly differentiates it from sibling list tools like list_blog_posts and list_categories.
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 (e.g., list_categories, list_offers). It does not mention prerequisites, filtering behavior beyond the optional 'q' parameter, or when not to use it. Usage context is only implied.
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 domain (booking, events, places, food, movies, etc.) with clear boundaries. Even similar actions like reservations are clearly differentiated by context (booking appointment vs. table vs. event tickets vs. RSVP).
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_events, search_places). No mixing of conventions or vague verbs.
28 tools is on the higher end but justifiable for a comprehensive neighborhood directory covering bookings, events, store, reviews, FAQs, guides, offers, movies, and more. Each tool serves a specific purpose without redundancy.
The tool surface covers the main user workflows (searching places, booking services, events, food ordering, loyalty, reviews). Minor gaps like lack of user account management or direct payment handling are acceptable for a directory MCP.