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?
Discloses that it returns all FAQs grouped by category. No annotations provided, but the description adequately conveys read-only behavior. Lacks mention of pagination or limits.
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, front-loaded with purpose, no redundant words. Highly concise.
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, no-output-schema tool, the description fully informs an agent about purpose and appropriate use cases.
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 exist, and schema coverage is 100%. The description's note about grouping adds value, earning a baseline score of 4 for zero-parameter tools.
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 it retrieves all FAQ questions and answers grouped by category, and specifies the use case for answering common site questions. This differentiates it from sibling list tools.
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 usage guidance: 'Use this to answer common questions about the site — opening hours, parking, policies, etc.' Does not mention when not to use, but context is sufficient.
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 action, with clear boundaries between similar operations (e.g., create_booking vs request_reservation vs reserve_event_tickets). Descriptions provide enough context to avoid confusion.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., create_booking, get_availability, list_events. No mixing of styles or ambiguous verbs.
28 tools is slightly above average but appropriate for a multi-feature neighborhood directory covering bookings, events, movies, menus, forms, etc. Each tool serves a distinct purpose, justifying the count.
The tool set covers most expected operations for a directory site: search, details, reviews, booking, events, menus, blog, FAQ, forms, etc. Minor gaps like cancellation or user booking history are acceptable given the domain scope.