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 must cover behavioral traits. It mentions returned fields but omits critical details: that it's read-only, supports pagination via limit, default ordering, and whether it returns all or active products 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?
Two sentences, no redundant information, front-loaded with the core purpose. Every word earns its place.
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 and no annotations, the description should provide more context about return behavior (e.g., pagination, sorting, defaults). It covers returned fields but lacks completeness for full agent understanding.
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 covers both parameters with descriptions. Description does not add any extra meaning or usage guidance beyond the schema, meeting baseline expectation.
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?
Clearly describes the action (list products in Wix Stores) and the resource (products). Distinguishes from sibling tools as no other list tool targets products. Returns specific fields.
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?
Implied usage by stating 'List products in this site's store', which informs the agent when to use it. No explicit alternatives, but siblings don't offer product listing, so it's clear.
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 (e.g., bookings, events, places, restaurants, movies, forms) with clear boundaries. Even similar actions like create_booking and request_reservation are differentiated by service type (appointment vs restaurant table) and payment flow.
All 28 tools follow the consistent verb_noun snake_case pattern (e.g., create_booking, list_events, search_places). Verbs are appropriate and predictable, with no mixing of conventions.
28 tools is slightly above the typical range, but each tool serves a distinct purpose within the comprehensive neighborhood directory domain. The count is justified by the breadth of features (booking, events, restaurants, movies, etc.).
The tool surface covers most user needs: searching, viewing details, booking, reservations, events, forms, and more. Minor gaps exist, such as no cancellation tools for bookings/reservations, but the core workflows are well-supported.