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 fully disclose behavior. It only states it lists products and returns certain fields. It does not mention that it is read-only, any authentication needs, rate limits, pagination behavior, or side effects.
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?
Very concise single sentence. No wasted words, but could be expanded slightly without losing conciseness to cover usage or behavioral context.
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?
Adequate for listing a simple set of products with two optional parameters. However, lacking usage guidance and behavioral details for a tool with many siblings. No output schema so description should elaborate on return format but does not.
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 clear parameter descriptions. The description adds no additional meaning beyond the schema for the parameters, but the baseline score applies as the schema already carries the burden.
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 states it lists products in a Wix Stores site and specifies the returned fields (name, price, stock status, product type). This clearly differentiates it from sibling tools like list_blog_posts or list_events.
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 guidance on when to use this tool vs alternatives, such as when to use search queries or filtering. No mention of when not to use it or prerequisites like site configuration.
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 resource: booking appointments, restaurant reservations, event tickets, searches, etc. No two tools have overlapping purposes; even similar actions like create_booking and request_reservation are for different domains (appointments vs. restaurant tables).
All tools follow a consistent verb_noun pattern using lowercase and underscores (e.g., get_availability, list_events, create_booking). There is no mixing of styles like camelCase or inconsistent verbs.
28 tools is above the typical well-scoped range but each tool serves a clear purpose within the comprehensive neighborhood directory domain. The count feels justified, though slightly heavy.
The tool set covers most major features of a neighborhood directory: places, events, booking, restaurant menus, reviews, forms, etc. Minor gaps exist, such as no create_review or update operations, but core workflows are complete.