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 must disclose behavioral traits. It states that results are grouped by category, which is helpful. However, it does not mention authentication, rate limits, or what happens if no FAQs exist, leaving some gaps.
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, two sentences long with no unnecessary words. It front-loads the key action ('Get all FAQ') and provides immediate context for usage.
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 simple list tool with no parameters, the description covers the purpose, output grouping, and usage examples well. It lacks details on pagination or empty results, but given the simplicity, it is nearly complete.
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 the baseline is 4. The description adds value by explaining that the tool returns all FAQs grouped by category, providing context beyond the empty schema.
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 explicitly states the tool retrieves all FAQ questions and answers for the site, grouped by category. It distinguishes from sibling tools (e.g., list_blog_posts, list_forms) by specifying 'FAQ' and site-specific context.
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 clear usage context by stating 'Use this to answer common questions about the site' and gives examples like opening hours, parking, and policies. However, it does not explicitly mention when not to use it or direct to alternatives.
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.
Every tool has a clearly distinct purpose, with detailed descriptions that prevent ambiguity. Overlaps like create_booking vs request_reservation are clarified by domain (appointments vs restaurant) and mechanics.
All tool names follow a consistent verb_noun pattern (e.g., create_booking, list_events, search_places). The same conjugation style (snake_case) is used throughout, with no mixing of conventions.
At 28 tools, the set is slightly larger than the typical well-scoped range (3-15), but each tool corresponds to a distinct feature of the neighborhood directory, making the count reasonable for the breadth of functionality.
The tool surface covers all major user-facing actions: searching, browsing, booking, purchasing, and retrieving information. No obvious gaps exist for the stated purpose of a neighborhood directory.
