check_availabilityCheck whether Lilla Älva is available. Without arguments, returns all blocked (unavailable) date ranges from today onward. With check_in and check_out (YYYY-MM-DD), also states whether that stay is available. Ranges are all-day and end-exclusive: a new stay may begin on another booking's check-out day.
| Name | Required | Description | Default |
|---|---|---|---|
| check_in | No | ||
| check_out | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It discloses that output is blocked date ranges from today onward, that ranges are all-day, and that they are end-exclusive so a stay can start on another booking's checkout day. This is useful behavioral detail beyond the schema.
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?
Three sentences, no wasted words. The main purpose is front-loaded, and the important boundary semantics are packed into the final sentence without bloat.
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 two-optional-parameter tool with no output schema, the description covers the core behavior and date boundary semantics. It could specify response structure or behavior for invalid/partial parameters, but the essential calling contract is clear.
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 description coverage is 0%, but the description compensates by naming check_in/check_out, specifying YYYY-MM-DD format, and explaining how they alter the result. It could add more about handling only one parameter, but it clearly establishes the intended combined usage.
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 opens with a specific verb and resource: 'Check whether Lilla Älva is available.' It then clarifies two distinct modes, which distinguishes it from siblings like get_property_info, get_quote, and submit_booking_request.
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 gives clear context for both invocation modes: without arguments it returns all blocked ranges, with check_in/check_out it checks a specific stay. It does not explicitly name alternatives or exclusions, but the usage intent is unambiguous.
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 serves a clearly distinct function: availability checking, property information, pricing, and booking submission. There is no overlap between the four tools, so an agent can easily select the right one for the current step.
All tool names follow a consistent verb_noun pattern with clear, descriptive verbs (check, get, get, submit). The naming style is uniform snake_case and each name clearly signals its purpose.
Four tools is exactly the right scope for a single-property booking server. Each tool covers a necessary part of the guest booking flow without redundancy or bloat.
The booking lifecycle is fully covered for this domain: guest can discover property details, check availability, obtain a price quote, and submit a booking request. Since bookings are confirmed manually by the owner via email, no additional booking management tools are needed.