Get all FAQ questions and answers for this site (Wix FAQ). Grouped by category. Use this to answer common questions about the site — opening hours, parking, policies, etc.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It states 'Get all' which implies a read operation, and mentions grouping. However, it does not disclose details like whether the result is paginated, limit, or structure of the response.
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 wasted words. Front-loaded with the action 'Get all FAQ questions and answers'. Followed by grouping info and usage guidance.
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 read tool with no parameters and no output schema, the description covers the essential: what it returns and when to use it. Could have hinted at the return format (e.g., list with question, answer, category), but overall adequate.
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?
No parameters, so baseline is 4. The description adds meaning beyond the empty schema by explaining the tool's output (FAQs grouped by category) and typical use cases.
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 gets all FAQ questions and answers for the site, grouped by category. Distinguishes from sibling tools like list_blog_posts by specifying 'FAQ' and providing example uses (opening hours, parking).
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?
Explicitly says to use this tool to answer common questions about the site, with concrete examples. Lacks explicit when-not-to-use, but context implies it's for simple FAQ lookups, not specialized queries.
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.
