List bookable time slots for a business on a given date and party size. Offer the guest only slots where available is true.
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | YYYY-MM-DD, in the venue's local calendar. | |
| slug | Yes | ||
| party_size | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It conveys a read-only list operation and the filtering behavior around 'available is true', which is useful. However, it does not mention response shape, edge cases, pagination, or explicitly state that it does not create a booking.
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?
Two concise sentences, front-loaded with the core action and followed by a practical instruction. Every sentence earns its place and there is no redundant filler.
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?
Adequate for a simple availability-listing tool, but with no output schema and no annotations, the description leaves out details about the returned slot structure and behavior when no slots are available. It gives enough to invoke correctly, but not complete clarity on the result.
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 only 33%, so the description must compensate. It maps slug to 'a business', and mentions date and party size in context, providing some added meaning. However, it does not fully describe slug's source/format or party_size semantics beyond the schema's minimum.
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?
States a specific verb ('List') and resource ('bookable time slots'), scoped by date and party size. The added instruction to only offer slots where available is true differentiates it clearly from sibling tools like create_booking and search.
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 implies when to use this tool: when checking what times can be booked for a business on a given date and party size. It does not explicitly name alternatives or exclusion conditions, but the context is clear and 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.
check_availability, create_booking, and search are clearly distinct, but fetch and get_business overlap heavily: both retrieve business details, differing only by whether you have an id or a slug. An agent could confuse one for the other and still get largely the same information.
Most tools follow a clear verb_noun pattern: check_availability, create_booking, get_business. However, fetch and search are bare verbs that do not include their object, which is a minor deviation from the otherwise consistent style.
Five tools is well-scoped for a booking-focused server. Each tool maps to a distinct step in the business discovery and reservation flow without unnecessary duplication or bloat.
The core guest journey is covered: search for a business, retrieve details, check availability, and create a booking. Missing booking lookup or cancellation tools are notable gaps, but they are not required for the primary make-a-reservation workflow.