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?
The description discloses that the tool returns all FAQs grouped by category, which is sufficient for a simple read-only operation. No annotations are provided, so the description carries the burden, but it lacks details about potential limitations (e.g., if the site has no FAQs or if there are rate 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 efficient sentences: the first states the action and resource, the second gives usage guidance. No waste, perfectly front-loaded.
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?
The description is complete for a simple list tool with no parameters, no output schema, and no annotations. It adequately covers what the tool returns and when to use it, though it could note that it returns all FAQs without filtering options.
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 no parameters, so the description doesn't need to explain them. It adds value by describing the output structure (grouped by category) and providing usage examples, which compensates for the lack of parameters.
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 tool's purpose: to retrieve all FAQ questions and answers for the site, grouped by category. It also gives specific examples of content (opening hours, parking, policies), making it highly specific and distinguishable from sibling 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?
The description explicitly says 'Use this to answer common questions about the site', providing strong context for when to invoke the tool. However, it does not mention when not to use it or alternatives, which would improve clarity.
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: booking appointments, restaurant reservations, event tickets, searches, etc. No two tools have overlapping purposes; even similar actions like create_booking and request_reservation are for different domains (appointments vs. restaurant tables).
All tools follow a consistent verb_noun pattern using lowercase and underscores (e.g., get_availability, list_events, create_booking). There is no mixing of styles like camelCase or inconsistent verbs.
28 tools is above the typical well-scoped range but each tool serves a clear purpose within the comprehensive neighborhood directory domain. The count feels justified, though slightly heavy.
The tool set covers most major features of a neighborhood directory: places, events, booking, restaurant menus, reviews, forms, etc. Minor gaps exist, such as no create_review or update operations, but core workflows are complete.