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 provided, so description carries full burden. It describes the tool as fetching and grouping data, implying a safe read operation, but does not explicitly state no side effects, auth requirements, or rate limits. Adequate but not comprehensive.
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: first states purpose and grouping, second gives usage examples. Every sentence is valuable, no redundancy, front-loaded with the main action.
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?
With no output schema, description mentions grouping by category and provides examples of content (opening hours, parking, policies). It gives enough context for the agent to understand the tool's role, though return field names are not specified.
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?
Input schema has no parameters (0 params), and schema coverage is 100% by default. Baseline is 4, and description does not need to add parameter info. It does not provide any parameter semantics, which is acceptable.
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?
Description states a specific verb 'Get' and resource 'FAQ questions and answers', and mentions grouping by category. It is clearly distinct 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?
Explicitly says 'Use this to answer common questions about the site — opening hours, parking, policies, etc.' This provides clear context for when to use, but does not mention when not to use or 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 action and resource, such as booking, checking availability, listing events, or searching dishes. No two tools appear to overlap in purpose, and descriptions clearly differentiate them.
All tools follow a consistent verb_noun pattern (e.g., create_booking, get_availability, list_events, search_places). The prefixes (create, get, list, search, request, reserve, rsvp, submit) are uniformly applied, and there is no mixing of cases or styles.
With 28 tools, the server covers a broad feature set for a neighborhood directory, including bookings, store, events, loyalty, menus, movies, and more. While slightly high, each tool serves a distinct purpose and is justifiable.
The tool surface appears complete for the domain: search, details, booking flows, store purchases, events, loyalty, reviews, blog, offers, profiles, forms, and FAQ are all covered. There are no obvious dead ends, and operations for CRUD or lifecycle are present where needed.