List curated editorial guides ("best of" lists) published by this site — ranked places with editorial notes. The best source for "best X in this neighborhood" questions.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max guides to return (default 20, max 50). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool lists guides (read operation) and that they are published by this site, but lacks details on rate limits, authentication needs, or any side effects. Basic transparency is adequate for a simple list tool.
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 concise, consisting of two sentences that deliver the key information without extraneous words. It efficiently communicates the tool's purpose and usage context.
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 the tool's simplicity and lack of output schema, the description provides good context: it states the content (editorial guides, ranked places with notes) and usage scenario. However, it could briefly mention the return format or structure of the guides to be fully 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?
The only parameter, 'limit', has 100% schema coverage with a description in the schema. The tool description does not add extra meaning beyond what the schema provides, so the baseline score of 3 is appropriate.
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 'curated editorial guides' ('best of' lists). It distinguishes from sibling list tools by specifying editorial guides with ranked places and editorial notes, making the purpose unambiguous.
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: 'The best source for "best X in this neighborhood" questions.' It implies the tool is ideal for finding recommendations but does not explicitly state when to use alternatives like search_places.
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 or action (booking, checkout, availability, events, reviews, etc.). Even similar-looking tools like create_booking, request_reservation, and rsvp_event are clearly differentiated by their descriptions and target systems.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_booking_services). No mixing of conventions or unclear verbs.
28 tools is on the higher end, but the server covers a wide domain (places, events, movies, booking, forms, loyalty, etc.). Each tool serves a clear purpose, so the count is justifiable, though minor trimming could be considered.
The tool set covers most workflows for a neighborhood directory: search, details, booking, events, reviews, etc. Some CRUD operations are missing (no update/delete for bookings), but these are consumer-facing actions where that is acceptable. The domain is well-covered.
