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, the description carries full burden. It discloses return fields and the special behavior of FLASH offers (countdown deadline), but does not mention pagination, ordering, or that it is read-only. The purpose is clear but additional behavioral traits are implicit.
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 is three concise sentences with no fluff. It front-loads the purpose, lists returned fields, and adds a key detail about FLASH offers. Every sentence adds value.
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?
Given no output schema, the description adequately explains return values. For a list tool with only two optional parameters, it covers essential context. It does not mention ordering or default limit but the schema covers that. Sibling differentiation is present, making it contextually complete for an agent.
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 mentions FLASH offers which relates to the 'kind' parameter, but adds no new information beyond the schema's own description. The 'limit' parameter is not referenced in the description.
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, specifying its output fields (discount label, promo code, CTA link, validity window, business). It distinguishes itself from sibling tools like list_products or list_pricing_plans by focusing on time-limited promotions, including explicit mention of FLASH 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?
The description provides no guidance on when to use this tool versus alternatives like get_loyalty_info or list_pricing_plans. It does not include exclusionary context or typical use cases, leaving the agent to infer suitability.
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 operation: bookings, restaurants, events, forms, etc. Even similar actions like create_booking and request_reservation are clearly differentiated by domain and description.
Tools follow a consistent verb_noun pattern (e.g., create_booking, get_availability, list_blog_posts). Collection retrieval uses list_ while single item uses get_, which is a standard and clear convention.
28 tools is on the upper end, but each serves a distinct function for a comprehensive neighborhood directory (places, events, booking, forms, etc.). No obvious bloat given the scope.
The tool surface covers all major user intents for a local directory: searching places, getting menus, booking services, viewing events, submitting forms, etc. No critical gaps are apparent.