Get the service catalog for a local service business, including service names, descriptions, estimated durations, price ranges, max participants, booking start policy, and whether the customer's address is required to book. Always available for any business.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The exact URL slug returned by search_businesses or get_business_info. Copy it verbatim. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds value by listing the exact return fields (price ranges, booking start policy, address requirement) and the 'always available' guarantee, which provides behavioral context beyond the annotations. It does not disclose edge cases like invalid slugs, but that is covered by the schema's 'exact URL slug' instruction.
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?
A single, information-dense sentence that front-loads the primary action ('Get the service catalog') and lists the key return elements. Every word adds value, and there is no redundancy or 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?
For a simple read-only tool with one fully-documented parameter, no output schema, and strong annotations, the description sufficiently covers the return content and availability. It explains what the tool returns and confirms it works for any business, making the tool fully understandable for an agent.
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 100% for the single 'slug' parameter, with clear guidance to copy it verbatim from search_businesses or get_business_info. The tool description itself adds no additional parameter semantics, so the baseline 3 applies.
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 'Get the service catalog for a local service business' and enumerates specific content (service names, durations, price ranges, etc.), which strongly distinguishes it from sibling tools like get_pricing (pricing-only) or get_business_info (business details). The verb+resource+scope pattern is clear and specific.
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 clear context with 'Always available for any business' implying no prerequisites or restrictions. However, it does not explicitly mention when to use it versus alternatives (e.g., 'use this instead of get_pricing when you need the full service catalog'), so it lacks explicit exclusion guidance.
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: discovery, refinement, business details, services, pricing, availability, booking, inquiry, and agent chat. Even the two availability tools are clearly separated by scope (specific business/service/date vs. cross-business soonest slots). No two tools appear to do the same thing.
All tool names follow a consistent snake_case verb_noun pattern (search_businesses, get_business_info, book_appointment, etc.). Verbs are varied but each is semantically precise, and there are no punctuation or style inconsistencies.
With 10 tools, the server is well-scoped for its purpose: covering the full local-business discovery-to-booking journey. Each tool earns its place and there is no redundancy or bloat.
The tool surface comprehensively covers the domain: search, refinement, info, services, pricing, availability (both specific and cross-business), booking, inquiry, and agent interaction. There are no missing critical operations for the stated purpose of discovering, contacting, and booking local service businesses.
