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 bears full responsibility. It clearly states the tool retrieves all FAQ questions and answers grouped by category, which is a straightforward read operation. However, it omits any mention of potential pagination or rate limits, though these are unlikely given zero parameters.
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 succinct sentences, front-loaded with the core functionality, then usage guidance. Every word serves a purpose 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 parameter-less tool with no output schema, the description fully covers what the tool returns and when to use it. It is complete for the given complexity.
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 no parameters, so per the rubric baseline is 4. The description adds no parameter details because none exist, and schema coverage is trivially 100%.
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 uses the specific verb 'Get' and resource 'FAQ questions and answers for this site', clearly distinguishing it from sibling tools like list_blog_posts or list_products. The mention of grouping by category adds further clarity.
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 explicitly states when to use the tool: 'to answer common questions about the site — opening hours, parking, policies, etc.' It provides clear context but does not explicitly exclude other scenarios or name alternative tools, which would elevate it to a 5.
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: appointments, products, events, places, menus, reviews, forms, etc. No two tools have overlapping purposes; even similar booking tools (create_booking, request_reservation, reserve_event_tickets, rsvp_event) are clearly differentiated by description and use case.
All tool names follow a consistent verb_noun pattern using lowercase with underscores (e.g., create_booking, list_events, search_places). Verbs are appropriate (create, get, list, search, submit, request, reserve, rsvp) and nouns clearly indicate the resource.
28 tools cover a broad domain (neighborhood directory with Wix integrations). While each tool has a clear purpose, the count exceeds the typical 3-15 range slightly, making the surface feel somewhat heavy but still manageable.
The tool surface provides comprehensive coverage for the domain: discovery (search places, list events, list guides), details (get place, get reviews), booking (appointments, restaurant, event tickets, RSVP), checkout, forms, FAQs, loyalty, pricing plans, and more. No obvious dead ends for common user journeys.
