Look up a business on G-Guest: services, opening hours, timezone and maximum party size. Call this first if you only know the slug.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Business identifier, e.g. "demo". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden itself. It communicates that this is a lookup operation and discloses the key returned business attributes. It does not mention error behavior, but for a simple slug-based lookup the provided context is adequate.
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 short sentences, front-loads the tool's core purpose and return fields, and ends with a practical usage directive. Every sentence contributes value without redundancy.
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?
This is a simple one-parameter lookup tool with no output schema. The description provides the resource, the returned fields, and a clear usage condition, which is sufficient for an agent to select and invoke the tool correctly.
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%, so the schema already documents the slug parameter fully. The description adds light usage context by referencing the slug, but it does not add new parameter format or constraint information beyond what the schema provides.
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 looks up a business on G-Guest and lists the returned data: services, opening hours, timezone, and maximum party size. It is specific about the resource and action, though it does not explicitly name or contrast sibling tools to differentiate them.
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 gives clear usage context: "Call this first if you only know the slug." This tells an agent when to prefer this tool, but it does not mention alternatives or explicit exclusions, so it falls just short of a full 5.
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.
check_availability, create_booking, and search are clearly distinct, but fetch and get_business overlap heavily: both retrieve business details, differing only by whether you have an id or a slug. An agent could confuse one for the other and still get largely the same information.
Most tools follow a clear verb_noun pattern: check_availability, create_booking, get_business. However, fetch and search are bare verbs that do not include their object, which is a minor deviation from the otherwise consistent style.
Five tools is well-scoped for a booking-focused server. Each tool maps to a distinct step in the business discovery and reservation flow without unnecessary duplication or bloat.
The core guest journey is covered: search for a business, retrieve details, check availability, and create a booking. Missing booking lookup or cancellation tools are notable gaps, but they are not required for the primary make-a-reservation workflow.