Find restaurants near several places, with open slots

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the read-only/open-world annotations, the description discloses several important behavioral traits: unset options come from saved preferences, walking time is estimated from map distance rather than transit, the call takes 30 seconds to 2 minutes, and the result includes walking minutes and open times. These are exactly the operational details an agent needs before invoking it.

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 short, front-loaded with the primary purpose, and every sentence adds useful information about scope, defaults, estimation caveats, or latency. There is no filler.

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 13-parameter search tool with no output schema, the description is largely complete: it explains what is returned, how defaults are applied, and the main caveat about walking-time estimation. It stops short of mentioning some parameters such as budget and max_results, but those are partly covered by the schema.

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?

With only 54% schema description coverage across 13 parameters, the description meaningfully supplements the schema by documenting defaults for unset options: dinner 17:00–20:00, business private room, and 15-minute walking limit. It also explains that walking time is an estimate. It does not cover every parameter, but it adds important semantics 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?

The description names a specific verb and resource: it finds restaurants within walking range of multiple locations that are bookable online. It is clearly a search tool and conveys the business-dinner context. It does not explicitly distinguish itself from the sibling search_restaurants or get_availability tools, so a 4 rather than a 5.

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 frames this as the main search for business dinners and describes the intended context: locations, bookable slots over the next days, optional private room. It does not explicitly name alternatives or say when not to use it, so it lacks the explicit routing guidance of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.