get_campsite_detailsGet full details for a specific campsite or accommodation by its ID. Returns description, all features/amenities, address, photos, rating, accommodation types offered, and booking information.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | Yes | The unique entity ID of the campsite |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds valuable context by enumerating the returned data (features, address, photos, rating, etc.), which is not present in the schema or annotations. This clarifies what the agent can expect from the response.
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, well-structured sentence. It begins with the action and resource, then lists the key return fields without superfluous wording. Every part adds value, making it appropriately concise.
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, one-parameter read-only getter with no output schema, the description provides sufficient context by naming the main response content. It does not discuss error cases or edge scenarios, but the low complexity and safe annotations make this acceptable. A small gap is that 'accommodation' is included but not elaborated, though not a blocker.
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 schema fully describes the only parameter (entity_id) with a clear description: 'The unique entity ID of the campsite'. The description's mention of 'by its ID' adds no new semantics. Since schema coverage is 100%, the baseline of 3 applies.
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 'Get' and the resource 'full details for a specific campsite or accommodation by its ID', distinguishing it from search-oriented siblings like search_campsites and list-type tools like get_features. The scope (by ID) is explicit and 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 clearly conveys when to use the tool: when you have an entity ID and need complete details for a specific campsite or accommodation. It does not explicitly name alternatives or exclusion criteria, but the context is strong enough that an agent can infer this is the detail-by-ID endpoint.
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: bk_* for Bookeasy booking workflows (add, checkout, guest, promo, search operators/content), get_* for retrieval, search_* for different domains (campsites, campervans, products), and find_nearest_toilets and recommend_gear for specific niche queries. No significant overlap.
Naming follows a consistent pattern: bk_ prefix for Bookeasy tools, then verb_noun (e.g., bk_cart_add, bk_search_operators). Non-bk tools use get_ or search_ prefixes. All snake_case, predictable and clear.
18 tools cover a broad scope (accommodation search, campervan rental, public toilets, weather, gear, products, and full booking lifecycle) without bloat. Each tool earns its place; the count is well-scoped for the domain.
The tool set covers most user needs: listing, searching, booking, weather, gear, product sales. Minor gaps (e.g., no tool for cancelling/viewing past bookings) but these are likely handled externally via the booking platform. The core workflows are well-supported.