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 provided, so description carries full burden. It mentions returned fields (name, price, stock status, product type) but does not disclose whether the operation is read-only, or describe pagination behavior beyond the limit parameter. Incomplete but not misleading.
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?
Two concise sentences with no redundant words. Front-loaded with the main purpose, followed by return field summary. Ideal structure.
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 or annotations, the description provides adequate context for a simple list operation with two optional parameters. Could mention pagination behavior or result format, but the return fields are specified.
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 describes both parameters fully (q and limit), so baseline is 3. The tool description adds no additional explanation beyond the schema.
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 action (list), resource (products), and scope (Wix Stores). It also lists the returned fields, making the purpose unambiguous. No sibling tool duplicates this functionality.
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?
No explicit guidance on when to use this tool versus alternatives like list_offers or search_dishes. The description implies its use for listing store products, but lacks when-not or alternative recommendations.
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 action and domain, with clear descriptions preventing confusion. Similar tools like create_booking, request_reservation, reserve_event_tickets, and rsvp_event are differentiated by service type and workflow.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_categories), ensuring predictability and ease of use for agents.
With 28 tools, the set is fairly large but appropriate for a comprehensive neighborhood directory covering multiple domains (places, events, booking, store, forms, etc.). Each tool serves a distinct purpose without redundancy.
The tool surface covers the full lifecycle of common user needs: search and discovery, detailed info, reservations, purchases, and interactions (forms, FAQs). No obvious gaps for the described purpose of a neighborhood directory.