Link the guest bookings you made with your email to your signed-in account so you can manage them from your account. Requires signing in (OAuth) with a verified email.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses OAuth requirement and verified email need, adding context beyond annotations which indicate idempotentHint=true but no contradictions.
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?
Single sentence with no wasted words, efficiently conveying purpose and prerequisites.
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?
Adequately covers purpose and requirements; slight gap on post-link effects, but overall complete for a zero-parameter tool with no output schema.
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, so baseline 4. Description provides sufficient context for a parameterless tool.
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 tool links guest bookings to the signed-in account, using specific verbs and distinguishing from siblings like 'create_account' which creates new accounts.
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 states when to use (to manage guest bookings) and prerequisites (OAuth, verified email), but does not explicitly mention when not to use or reference sibling alternatives.
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.
