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 are provided, so the description must disclose behavioral traits. It mentions returned fields but lacks detail on pagination, ordering, side effects, or authentication requirements. For a read-only list, this is adequate but not thorough.
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 the verb 'List' upfront. Every word adds value; no redundancy or irrelevant 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 no output schema, the description should explain return values, which it does partially. However, it omits pagination behavior, default limit, and ordering, leaving some gaps for a list tool.
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 described. The description does not add new semantics beyond the schema, so a 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 the tool lists products in a Wix Stores context, specifying returned fields (name, price, stock status, product type). It distinguishes from sibling list tools by resource type.
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 for listing products but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.
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 and action. Even similar operations like create_booking, request_reservation, reserve_event_tickets, and rsvp_event are clearly differentiated by their descriptions and the entities they handle (bookable services, restaurant tables, paid events, free events). No two tools appear to do the same thing.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., create_booking, get_availability, list_events, search_places). This uniform convention makes the tool set predictable and easy for an agent to understand and select from.
With 28 tools, the set is relatively large, exceeding the typical well-scoped range of 3-15. While each tool serves a specific purpose within the neighborhood directory domain, the count feels heavy and may overwhelm simple use cases. A reduction or grouping could improve coherence.
The tool set covers a broad range of user-facing operations for a neighborhood directory: searching places, browsing menus, booking services, reserving tables and event tickets, listing products and events, retrieving reviews and FAQs, and submitting forms. Minor gaps exist (e.g., no cancellation or create_review tool), but the core workflows are well-supported.
