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 are provided, so the description carries the full burden. It states the tool retrieves data ('Get all FAQ'), implying a read-only operation, but does not explicitly declare its safety profile or any side effects. A clearer statement of read-only behavior would improve this score.
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 with no wasted words. The first sentence states the function and structure, the second gives usage guidance. Information is front-loaded and efficient.
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 parameters and no output schema, the description is mostly complete: it explains the return content (all FAQs, grouped by category) and usage. It lacks details on potential filtering or pagination, but for a simple list tool, it suffices.
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 input schema has zero parameters, so schema description coverage is effectively 100%. The description adds context about grouping by category, which is not in the schema. Since no parameters exist, the baseline is 4, and the description meets expectations.
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 retrieves all FAQ questions and answers, grouped by category. It explicitly mentions the resource (FAQ) and the action (get all), distinguishing it from sibling tools like list_blog_posts or list_products.
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 explicit usage context: 'Use this to answer common questions about the site — opening hours, parking, policies, etc.' This guides the agent on when to invoke the tool, though it does not explicitly mention when not to use it or list alternative tools.
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 (booking, events, places, food, movies, etc.) with clear boundaries. Even similar actions like reservations are clearly differentiated by context (booking appointment vs. table vs. event tickets vs. RSVP).
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_events, search_places). No mixing of conventions or vague verbs.
28 tools is on the higher end but justifiable for a comprehensive neighborhood directory covering bookings, events, store, reviews, FAQs, guides, offers, movies, and more. Each tool serves a specific purpose without redundancy.
The tool surface covers the main user workflows (searching places, booking services, events, food ordering, loyalty, reviews). Minor gaps like lack of user account management or direct payment handling are acceptable for a directory MCP.