Find restaurants by location, cuisine, price range, open-now filter. Cost: $0.25.
| Name | Required | Description | Default |
|---|---|---|---|
| price | No | Price range | |
| cuisine | No | Cuisine type (e.g. Hawaiian, Japanese, Mexican) | |
| location | Yes | Location to search (e.g. Waikiki, Kailua, Lahaina) | |
| open_now | No | Filter for currently open restaurants |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Only the cost ($0.25) is disclosed as behavioral information. No annotations exist, so the description should cover permissions, limitations, or response behavior. It lacks details on data freshness, error states, 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 very short and front-loaded with purpose, but it omits important details that would justify its length. It is not verbose but could be more structured to include usage notes.
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?
Given no output schema and empty annotations, the description is insufficient. It does not explain return format, pagination, or success/failure behavior, leaving the agent with incomplete information 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% with all four parameters documented. The description lists the filters but adds no additional meaning beyond the schema. Baseline score of 3 is appropriate.
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 clearly states the tool finds restaurants with specific filter dimensions (location, cuisine, price range, open-now). This verb+resource combination distinguishes it from sibling 'get_restaurant_details' which likely returns details for a specific restaurant.
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?
No guidance provided on when to use this tool versus alternatives like 'get_restaurant_details'. The description does not mention prerequisites or when not to use it.
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.