List active promotions and deals available in this neighborhood directory. Returns discount label, promo code (if any), CTA link, validity window, and which business/place it belongs to. FLASH offers have a countdown deadline.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Filter by offer kind. FLASH = time-limited flash sale with countdown. Omit to return all active offers. | |
| limit | No | Max offers to return (default 20, max 60). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries burden. States it returns active offers and notes FLASH have countdowns, but doesn't confirm read-only nature or disclose any side effects, rate limits, or response ordering.
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?
Three sentences, front-loaded with purpose, no wasted words. Efficiently presents needed info.
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?
No output schema, but description lists return fields sufficiently. Could mention if offers are sorted or paginated, but for a list tool with 2 optional params, it's reasonably 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?
Schema coverage is 100%, so baseline 3. Description adds minimal value beyond schema: mentions FLASH but doesn't elaborate on limit default or behavior beyond 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?
Clearly states it lists active promotions and deals, specifies exact returned fields (discount label, promo code, etc.), and distinguishes FLASH offers. Differentiates from sibling list tools by focusing on offers.
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?
Implies use when wanting to retrieve offers, but lacks explicit guidance on when to use vs other list tools (e.g., list_products, list_events). No when-not-to or alternative recommendations.
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 resource and action (e.g., create_booking, create_checkout, request_reservation, reserve_event_tickets, rsvp_event all differ in purpose). Even similar-sounding tools like search_places and list_categories serve complementary roles (search vs taxonomy). No ambiguity.
All 28 tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_blog_posts). No mixing of conventions or vague verbs.
28 tools is above the typical 3-15 range but appropriate for the comprehensive scope of a neighborhood directory covering multiple Wix integrations (bookings, events, store, restaurants, etc.). Slightly heavy but well-scoped.
The tool surface covers the full lifecycle of a neighborhood directory: search, details, reviews, menus, booking, events, movies, offers, forms, FAQs, loyalty, etc. No obvious gaps; each domain has create/read/update/delete where applicable.