Get full details for a specific place by its URL slug, including opening hours, a precomputed open_now boolean, amenity attributes (slugs), a delivery array of curated delivery-app deep-links (ifood, rappi, uber-eats — each { platform, url }), ratings, address, and neighborhood.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | URL slug of the place, e.g. "cafe-example". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It implies a safe read operation ('Get') and lists expected data, but does not disclose error handling (e.g., invalid slug), authentication requirements, rate limits, or idempotency guarantees. Adequate but not thorough.
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 a single sentence that efficiently conveys the tool's purpose and outputs. It is front-loaded with the action and resource. Could be slightly more structured (e.g., bullet list of included fields) but is already clear and free of redundant words.
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 has one required parameter and no output schema, the description compensates by listing the main response fields (opening hours, open_now, attributes, delivery, ratings, address, neighborhood). It does not cover error cases or optional fields, but for a simple get-by-ID tool, it is sufficiently 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?
There is one parameter (slug) with a clear schema description including an example. The tool description adds minimal value beyond restating the schema's purpose. With 100% schema coverage, baseline 3 is appropriate; no extra insight is provided about parameter behavior or formatting.
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 specifies the action ('Get full details'), the resource ('a specific place'), the identifier method ('by its URL slug'), and lists included fields (opening hours, open_now, attributes, delivery, ratings, address, neighborhood). This distinguishes it from sibling tools like search_places (list) or get_site_info (site-level).
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 implicitly states to use this when you need detailed information about a known place identified by its slug. Although it doesn't explicitly exclude other uses or compare to alternatives, the context (sibling tools list) and the specific parameter make it clear. Slight lack of explicit when-not-to-use guidance prevents a 5.
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 action, with clear boundaries between similar operations (e.g., create_booking vs request_reservation vs reserve_event_tickets). Descriptions provide enough context to avoid confusion.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., create_booking, get_availability, list_events. No mixing of styles or ambiguous verbs.
28 tools is slightly above average but appropriate for a multi-feature neighborhood directory covering bookings, events, movies, menus, forms, etc. Each tool serves a distinct purpose, justifying the count.
The tool set covers most expected operations for a directory site: search, details, reviews, booking, events, menus, blog, FAQ, forms, etc. Minor gaps like cancellation or user booking history are acceptable given the domain scope.