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 exist, so description carries full burden. It discloses that the tool returns all FAQs grouped by category, which is the expected behavior. No side effects or destructive actions are implied, and the read-only nature is evident from 'Get all FAQ'. Could be improved by mentioning pagination or data freshness, but adequate.
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?
Extremely concise: two sentences that front-load the primary purpose and provide immediate usage context. Every word adds value.
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 parameterless tool with no output schema, the description is fully complete. It explains what data is returned (FAQs, grouped by category) and when to use it. No gaps.
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?
The tool has zero parameters and schema coverage is 100%. The description does not need to add parameter details. The baseline for no parameters is 4, and the description's mention of categories adds useful context.
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 the tool retrieves all FAQ questions and answers grouped by category, and specifies its use for answering common site questions like opening hours, parking, policies, etc. This distinguishes it from sibling tools like get_site_info or list_blog_posts.
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?
Provides explicit guidance on when to use this tool: 'Use this to answer common questions about the site'. It does not explicitly mention when not to use it or name alternatives, but the context is clear enough for an AI agent.
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.
All 28 tools have clearly distinct purposes. Overlaps like create_booking vs request_reservation are well-delineated by descriptions: one for appointments with checkout URL, the other for table requests via email confirmation. Similarly, reserve_event_tickets vs rsvp_event, and get_restaurant_menus vs search_dishes are complementary.
Tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_events, search_places). Verbs indicate action type (get/list for retrieval, create/reserve for creation), and nouns are specific entities. No mixing of conventions.
28 tools is above the typical 3-15 range but appropriate for the broad scope of a neighborhood directory with multiple Wix integrations (Bookings, Events, Stores, Reviews, etc.). Each tool covers a distinct feature, and no tool feels redundant.
The tool surface covers the main user workflows: searching places, viewing details and menus, checking availability, making bookings/reservations, and managing event tickets. Minor gaps exist (e.g., no update/cancel for bookings, no booking status check), but these are acceptable as the server focuses on initiating actions.