resy_search_venues

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

The description adds context beyond the readOnlyHint annotation by stating the tool returns 'venues including any bookable slot tokens', which implies read-only access to availability data. It does not contradict annotations and provides useful behavioral cues about the output.

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 with no redundant information. The first sentence states the core purpose, the second adds return format and default behavior. Every word serves a purpose, making it efficient for an agent to parse.

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 read-only search tool with 7 parameters and no output schema, the description covers the main outcome (venues with slot tokens), required inputs (date, party_size), and default geo. It does not detail optional parameters like limit or radius_meters, but the schema handles those. Minor gap: no guidance on when to use this over resy_find_slots, but overall sufficient.

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%, establishing a baseline of 3. The description adds value by explaining default geo behavior for lat/lng ('Defaults to NYC geo') and clarifying that date and party_size determine the slot tokens returned, enhancing parameter understanding 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 clearly states the verb 'Search' and resource 'Resy for restaurants with availability', distinguishing it from sibling tools like resy_find_slots (which operates on a specific venue) and resy_get_venue (which retrieves details). The mention of returning 'bookable slot tokens' specifies a unique output.

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 does not explicitly state when to use this tool versus alternatives like resy_find_slots or resy_get_venue. While the purpose indirectly suggests it for initial venue search, the lack of explicit 'when/when-not' guidance limits its value for an agent deciding between tools.

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