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?
With no annotations provided, the description carries full burden. It describes what the tool returns (discount label, promo code, etc.) and highlights FLASH offers' countdown, but does not disclose other behavioral traits like pagination, rate limits, or data freshness. 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 with zero waste. First sentence states purpose and return fields. Second sentence adds the important FLASH distinction. Every sentence earns its place.
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 two optional parameters, the description covers purpose, return fields, and a special case (FLASH). It does not explain pagination or ordering, but given the simplicity, it is fairly complete. Slight gap for a 5.
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 is 3. The description adds context for the 'kind' parameter (FLASH = time-limited) and mentions max limit of 60, but the schema already describes both parameters well. Minimal added value 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?
The description clearly states it lists active promotions and deals in a neighborhood directory, specifies return fields (discount label, promo code, CTA link, validity window, business/place), and distinguishes FLASH offers with countdown. This is specific and differentiates from siblings.
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 context for when to use this tool (listing active offers), but does not explicitly exclude alternative tools or state when not to use it. It mentions filtering by kind, which gives usage hints.
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., bookings, events, places, restaurants, movies, forms) with clear boundaries. Even similar actions like create_booking and request_reservation are differentiated by service type (appointment vs restaurant table) and payment flow.
All 28 tools follow the consistent verb_noun snake_case pattern (e.g., create_booking, list_events, search_places). Verbs are appropriate and predictable, with no mixing of conventions.
28 tools is slightly above the typical range, but each tool serves a distinct purpose within the comprehensive neighborhood directory domain. The count is justified by the breadth of features (booking, events, restaurants, movies, etc.).
The tool surface covers most user needs: searching, viewing details, booking, reservations, events, forms, and more. Minor gaps exist, such as no cancellation tools for bookings/reservations, but the core workflows are well-supported.