The two tools have perfectly distinct purposes: get_all_dishes retrieves a list of dish names, while get_dish_content fetches detailed content for a specific dish. There is no overlap or ambiguity between these operations.

Both tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming. The naming is predictable and clear across the set.

With only 2 tools, this server feels thin for a dish/recipe domain. While the tools cover basic retrieval, typical food-related servers would include operations like search, filter, create, update, or delete dishes for a more complete surface.

The server only provides read operations (list and get details), lacking any create, update, delete, or search capabilities. This is a significant gap that will limit agent workflows, as there's no way to modify or interact with dish data beyond viewing it.