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 the description carries the full burden. It discloses returned fields (discount label, promo code, CTA link, validity window, business/place) and notes that FLASH offers have a countdown deadline, but does not mention pagination, sorting, or what happens when no offers are active.
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 no fluff. The first sentence defines the core purpose, and the second adds important specificity about FLASH offers. 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?
The description lists returned fields but lacks an output schema. For a listing tool, details about pagination, default ordering, and response structure (array vs object) would improve completeness. Current description is adequate but not thorough.
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 the schema already describes both parameters. The description adds contextual value by explaining FLASH offers have a countdown deadline, which complements the kind enum. No extra semantics for the limit parameter.
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 'list' and the resource 'active promotions and deals in this neighborhood directory'. It distinguishes the resource from siblings like list_products or list_events by focusing on offers/promotions/deals, but does not explicitly call out differentiation.
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?
No guidance on when to use this tool versus alternatives like get_loyalty_info or list_pricing_plans. The description lacks explicit when/when-not context, leaving the agent to infer from the name alone.
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 on a specific resource (e.g., create_booking vs create_checkout vs reserve_event_tickets). Descriptions clearly differentiate purposes, and no two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_availability, list_categories, search_dishes). Verbs like get, list, create, request, rsvp are used uniformly, making the set predictable.
28 tools is above the typical 3-15 range, but the server covers a broad domain (places, events, movies, booking, store, etc.). Each tool serves a clear purpose, so the count is justified for the scope.
The tool surface is extensive, covering searching, details, reviews, booking, events, menus, etc. Minor gaps exist (e.g., no cancel/update operations), but they are likely intentional given the user-facing nature of the server.
