Get full details for a business including services (with IDs and prices), staff, and hours. You need service_id and optionally staff_id before calling book_appointment.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No | The business slug from search_businesses results | |
| business_slug | No | Alias for slug — the business slug from search_businesses results |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It clearly describes a read operation ('Get full details') and specifies the output, but does not explicitly state that it is read-only, free of side effects, or discuss any authorization requirements. The verb 'get' implies safety, but further context like no destructive actions is missing.
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?
The description is two sentences, front-loaded with the core purpose, followed by a relevant usage hint. Every sentence adds value; 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?
For a tool with 2 parameters and no output schema, the description covers the key outputs (services, staff, hours) and hints at the booking context. It does not detail every possible return field, but it is sufficient for understanding the tool's role among siblings. The lack of output schema is somewhat offset by the descriptive output list.
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?
The input schema has 100% coverage: both parameters have descriptions explaining they are business slugs from search_businesses. The tool description does not add additional parameter-level meaning beyond what the schema already provides, so it meets the baseline expectation.
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 retrieves full business details including services (with IDs/prices), staff, and hours. The verb 'Get' and resource 'business' are specific, and it distinguishes from siblings like search_businesses and get_availability by listing the output contents.
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 provides implicit guidance by stating the need to get service_id and optionally staff_id before calling book_appointment, indicating the tool's role in the booking workflow. However, it does not explicitly state when not to use it or compare to other sibling tools like get_booking or get_availability.
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.
