Get the food menu for a specific restaurant on this site. Returns menus with their sections, dishes, descriptions, prices, and dietary labels (vegan, gluten-free, etc). Use search_places or list_categories first to find the restaurant's place_slug.
| Name | Required | Description | Default |
|---|---|---|---|
| place_slug | Yes | The slug of the restaurant, e.g. "bar-do-ze" (from search_places or a place URL). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Although no annotations are provided, the description implies a read-only operation (getting the menu) and lists the expected return data. This provides sufficient transparency for a simple retrieval tool, though it does not cover potential edge cases like invalid slugs or rate limits.
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 concise sentences, front-loaded with the primary purpose, and no redundant words. It efficiently communicates the tool's function and necessary 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?
The description sufficiently covers the tool's output (menus with sections, dishes, descriptions, prices, dietary labels) and integrates the workflow with sibling tools. Without an output schema, this level of detail is appropriate for an agent to understand 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?
The schema description for place_slug already provides an example, and the description adds meaningful context by instructing the agent to use search_places or list_categories to obtain the value. Since schema coverage is 100%, baseline is 3, but the added guidance raises the score.
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 the food menu for a specific restaurant, including sections, dishes, descriptions, prices, and dietary labels. It distinguishes itself from siblings by specifying that place_slug is obtained via search_places or list_categories.
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 explicit guidance to use search_places or list_categories first to find the restaurant's place_slug, which helps the agent understand the prerequisite workflow. While it doesn't explicitly state when not to use the tool, the guidance is clear and actionable.
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 has a clearly distinct purpose, even among similar actions like booking, reservation, and ticket purchase—their descriptions clarify the domain and flow. No two tools could reasonably be confused.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_blog_posts). There are no deviations or mixed conventions.
At 28 tools, the surface is larger than ideal for a single server, but each tool covers a distinct feature of the neighborhood directory (bookings, events, store, etc.). It borders on heavy but is still manageable for an agent.
The tool set covers the full lifecycle of browsing and acting on a neighborhood directory: search, details, reviews, menus, events, booking, reservations, store, loyalty, and more. No obvious gaps exist for the intended use case.