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?
With no annotations, the description carries the transparency burden. It discloses that it is a read operation ('Get all') and that results are grouped by category, which is key behavioral context. It does not mention pagination or response format, but for a simple FAQ list this is acceptable.
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 concise and front-loaded, stating the purpose first, then grouping behavior, then usage guidance. Every sentence adds value with no redundancy.
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 no-parameter list tool without an output schema, the description sufficiently covers what the tool does, how results are organized (by category), and when to use it. No critical gaps are identified.
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?
There are zero parameters, so schema coverage is 100%. The description does not need to add parameter semantics, and the baseline for no parameters is 4.
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 verb 'Get' and the specific resource 'all FAQ questions and answers' for the site, and distinguishes it from sibling tools by focusing on FAQ content and category grouping.
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?
It provides clear usage context with 'Use this to answer common questions about the site — opening hours, parking, policies, etc.' It does not explicitly name alternatives or exclusions, but the guidance is sufficient for an agent to know when to select this tool.
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 resource or action (e.g., create_booking vs create_checkout, reserve_event_tickets vs rsvp_event), and descriptions provide clear boundaries. Even closely related tools like list_booking_services and list_pricing_plans are differentiated by context.
All 26 tools follow a consistent snake_case verb_noun pattern (get_, list_, create_, search_, etc.), with no mixed conventions or vague verbs. This makes the tool set predictable and easy to navigate.
At 26 tools, the set is on the heavy side and exceeds the typical well-scoped range, but the diversity reflects a multi-featured directory covering bookings, events, store, reviews, forms, and more. Each tool appears to serve a distinct purpose, so the count is borderline rather than excessive.
The surface covers the core user workflows: search, view details, book services, reserve/RSVP events, request reservations, submit forms, and browse content. Minor gaps exist (e.g., no cancellation/update for bookings, no full blog post body), but these are workarounds and not critical for a consumer-facing directory.
