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?
No annotations exist, so description carries full burden. It fully discloses that the tool returns menus with sections, dishes, descriptions, prices, and dietary labels. No side effects or destructive actions are mentioned (and none expected). Could have mentioned error behavior for invalid slugs, but otherwise transparent.
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?
Two sentences, each earning its place. First sentence defines purpose and output; second sentence provides necessary usage hint. No fluff or 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?
For a simple tool with one parameter and no output schema, the description is largely complete. It explains what is returned and how to get the input. Lacks details on error handling or return format, but these are minor given the tool's simplicity.
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?
Input schema already describes place_slug (100% coverage). Description adds concrete example ('bar-do-ze') and source (from search_places or place URL), providing extra context beyond the schema.
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?
Description states it gets the food menu for a specific restaurant and lists the returned items (sections, dishes, descriptions, prices, dietary labels). It clearly distinguishes from siblings like search_places (for finding the slug) and search_dishes (for dish-level search).
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 advises using search_places or list_categories first to obtain the required place_slug. This provides clear when-to-use guidance, though it does not explicitly list alternatives or when not to use, which is acceptable given the tool's straightforward purpose.
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 resource or action (e.g., bookings, events, places, menus, forms), with detailed descriptions that clearly differentiate even similar operations like create_booking vs. reserve_event_tickets. No two tools overlap in purpose.
All tool names follow a consistent verb_noun pattern using lowercase and underscores (e.g., create_booking, get_availability, list_events). Verbs are semantically appropriate (create, get, list, search, submit) and predictable.
28 tools is slightly above the typical 3-15 range, but the breadth of the neighborhood directory domain justifies each tool. The count feels dense but not excessive, with no redundant tools.
The tool set covers the full lifecycle of a neighborhood directory: place search, restaurant menus, events, movie showtimes, booking, reviews, blog, guides, offers, loyalty, forms, and profiles. Obvious gaps like review creation are absent but likely out of scope.
