List curated editorial guides ("best of" lists) published by this site — ranked places with editorial notes. The best source for "best X in this neighborhood" questions.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max guides to return (default 20, max 50). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It discloses that the guides are curated, editorial, and ranked, implying read-only behavior. However, it does not mention any potential rate limits, authentication needs, or other behavioral traits.
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 two sentences long with no wasted words. First sentence defines what the tool does; second sentence clarifies the use case. Highly concise and front-loaded.
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 one optional parameter, the description is fairly complete. It explains the nature of guides and when to use them. The lack of an output schema is acceptable as the return values are implicit.
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?
With 100% schema description coverage, the description adds no additional meaning beyond the schema, which already documents the 'limit' parameter. The baseline 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 curated editorial guides ('best of' lists) with ranked places and editorial notes. It explicitly distinguishes itself as the best source for 'best X in this neighborhood' questions, differentiating from sibling tools like search_places.
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 provides clear guidance on when to use the tool: for finding 'best of' guides. It suggests the context ('best X in this neighborhood' questions) but does not explicitly state when not to use it or compare to alternatives.
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.
Every tool targets a distinct Wix resource or action: bookings, events, store, forms, places, menus, etc. The four booking-related tools are clearly separated by domain (appointments, restaurant tables, paid events, free events), with descriptions that eliminate ambiguity.
The set follows a consistent verb_noun snake_case pattern (create_, get_, list_, search_, submit_). Minor deviations exist: get_reviews and get_event_tickets return collections (could be list_), and rsvp_event uses an abbreviation, but these do not affect clarity.
At 26 tools, the set is larger than the typical 3–15 well-scoped range, but the server covers a broad umbrella of Wix integrations for a neighborhood directory. Each tool maps to a distinct function, so the count is justified by the scope, though it is on the heavier side.
The surface covers discovery and transactional workflows: searching places/dishes, viewing menus/reviews/guides/offers, booking appointments and tables, reserving event tickets, purchasing products, submitting forms, and reading site info. Minor gaps exist (no cancel/update operations), but these are handled via external checkout links and are acceptable for a directory.
