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?
No annotations exist, so the description must fully cover behavioral traits. It mentions the return fields (name, price, stock status, product type) but does not disclose whether the operation is read-only, requires authentication, or has any side effects. Pagination behavior and error conditions are also omitted.
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, concise sentence that front-loads the primary action and resource. Every word adds value, with no repetition or filler.
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 list tool with 2 optional parameters and no output schema, the description is largely complete. It specifies return fields. The only minor gap is not describing pagination behavior (e.g., how to get next page) or any prerequisites (e.g., Wix Stores must be active).
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 covers 100% of parameters with descriptions, so the schema already provides meaning. The description adds a mention of product name matching for the 'q' parameter and default/max for 'limit', but these are already in the schema. No additional value beyond schema is provided.
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 action ('List products'), the resource ('products'), and the scope ('in this site's store (Wix Stores)'). It also specifies the return fields, making the purpose unambiguous.
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 context (listing products) but does not provide explicit guidance on when to use this tool versus alternatives (e.g., list_offers, list_pricing_plans). No when-not or exclusion criteria are mentioned.
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.
Tools are mostly distinct with clear descriptions. Some overlap in actions that require user to click a link (create_booking, create_checkout, request_reservation, etc.), but each targets a different domain (booking, store, restaurant, event tickets, RSVP). Minor ambiguity possible but descriptions clarify.
All tools follow a consistent verb_noun snake_case pattern (e.g., create_booking, get_availability, search_places). No deviations or mixed conventions.
28 tools is slightly high for a neighborhood directory, but each serves a specific function (search, booking, events, movies, offers, etc.). The scope justifies the count, though some tools like list_blog_posts and list_faqs might be considered niche.
The tool set covers search, place details, categories, menus, events, movies, offers, booking, and forms. Missing update/delete operations for places or user management, but these are likely out of scope for a read-only directory. Core queries and actions are well-supported.
