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 bears full responsibility for behavioral disclosure. It describes the output (all FAQs grouped by category) and implies read-only behavior via the verb 'Get'. It does not address potential issues like pagination or data freshness, but for a simple retrieval tool, this is adequate and contains no contradictions.
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 consists of two concise sentences, front-loaded with the core action. Every sentence adds value: the first defines the tool's function, the second guides usage. No unnecessary words or repetition.
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 parameterless tool with no output schema, the description covers the essential aspects: what is returned (FAQs grouped by category) and when to use it (for common questions). While it could mention return format details or any limits, the provided information is sufficient for an AI agent to understand and correctly invoke the tool.
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, and schema description coverage is 100% (trivially). The description adds value by explaining the return structure (grouped by category), which is relevant context beyond the empty schema. Per the guidelines, 0 parameters yields a baseline of 4.
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 verb 'Get', the resource 'all FAQ questions and answers', and includes additional context like 'Grouped by category' and 'Wix FAQ'. It distinguishes itself from sibling tools like list_blog_posts by specifying the use case for answering common questions about the site.
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 this tool: 'Use this to answer common questions about the site — opening hours, parking, policies, etc.' It does not mention when not to use or list alternatives, but given no sibling tool overlaps in functionality, this is sufficient guidance.
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 (e.g., booking, restaurant reservation, event RSVP, movie showtimes) with clear descriptions that prevent confusion. Overlapping verbs like 'create' are used for different resource types, and the descriptions explicitly distinguish their contexts.
All 28 tools follow a strict verb_noun pattern with underscores, e.g., create_booking, get_availability, list_events. No mixing of conventions or inconsistent verb styles.
28 tools is at the upper end of reasonable for a broad neighborhood directory server covering places, bookings, events, movies, store, forms, and more. While each tool serves a distinct purpose, the count feels slightly high for a single server.
The tool surface covers core discovery and booking initiation (search, detail, book, reserve), but lacks lifecycle operations like cancel, update, or list user's existing bookings. Several operations require external checkout or confirmation links, creating workflow gaps.