list_available_timesReturn the open time slots for a booking page, identified by its slug or its full link. Each slot has an opaque id and a human-readable time label in the host's timezone. Pass a slot id to book_meeting — never invent a time; only these ids are bookable.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full disclosure burden. It reveals that slot ids are opaque, time labels are human-readable and in the host's timezone, and only returned ids are bookable. This goes beyond basic list semantics, though it omits minor details like empty-result or error behavior.
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 with zero filler: the core action is front-loaded, followed by the return-value shape and a critical routing note. Every sentence earns its place.
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 one-parameter tool with no output schema and no annotations, this description covers the essential context: return value shape, timezone, and how the output is used by book_meeting. Missing edge cases (e.g., what happens when no slots exist) are non-critical for correct invocation.
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%, so the description must compensate. It partially does by saying the page is identified by 'its slug or its full link', which adds meaning to the lone slug parameter. However, it doesn't specify the expected format of either, leaving ambiguity about whether the slug field accepts a full URL.
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 states a specific verb and resource: 'Return the open time slots for a booking page'. It clearly distinguishes itself from siblings by explicitly linking the output to book_meeting ('Pass a slot id to book_meeting'), which prevents confusion with get_booking and get_booking_page.
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?
Usage is explicitly routed: the description tells the agent to pass a returned slot id to book_meeting and warns never to invent a time. This is an unambiguous when-to-use that also names the sibling consuming the output, leaving no inference needed.
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 action and resource: book a meeting, fetch a booking, inspect a booking page, and list available slots. There is no overlap, and the intended use of each tool is immediately clear.
All tool names follow a consistent verb_noun pattern in snake_case: book_meeting, get_booking, get_booking_page, list_available_times. The verbs and nouns clearly indicate the operation and target.
Four tools cover the complete guest-side booking flow without unnecessary redundancy. This is a well-scoped size for a focused booking server.
The set covers the essential guest journey: view page, check availability, book, and retrieve booking status. A direct cancel or reschedule tool is missing, though the booking result provides a manage link, making this a minor gap rather than a dead end.