List all appointments booked with your email address. Requires signing in (OAuth) — your AI must be connected with an authenticated account that has a verified email. Returns your upcoming and past bookings.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already include readOnlyHint=true and openWorldHint=true. The description adds that it returns both upcoming and past bookings, and mentions auth requirements, providing value beyond annotations.
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-loading the purpose and prerequisites. No redundant information.
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?
Despite no output schema, description states return values (upcoming and past bookings). Auth requirement and zero parameters make this complete for a simple list tool.
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?
No parameters exist, and schema coverage is 100%. Baseline for 0 parameters is 4, and no additional parameter meaning is needed.
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 'List all appointments booked with your email address', specifying verb (list) and resource (appointments). This distinguishes it from siblings like get_booking or cancel_appointment.
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?
Explicitly mentions OAuth authentication requirement and verified email, which is crucial context. Does not explicitly exclude alternatives, but sibling tool names provide enough differentiation.
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: booking, cancellation, availability, business details, account management, etc. Even similar tools like get_booking and list_my_bookings have clear differences in parameters and scope.
All tools follow a consistent verb_noun pattern with underscores (e.g., book_appointment, get_availability, search_businesses). No mixed styles or irregular verbs.
11 tools is well-scoped for a booking marketplace, covering customer operations, account linking, and business signup without unnecessary duplication.
The tool surface covers the core customer journey (search, view, book, cancel, reschedule) and account management. Minor gaps like business-side booking management are likely out of scope.
