resy_find_slots

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

All annotations (readOnlyHint) are consistent with the description. The description adds important behavioral information about token expiration, which is beyond what annotations provide. No contradictions.

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, no wasted words, immediately states purpose. Efficiently structured.

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?

Explains purpose, return value (tokens), and expiration warning. Lacks details on optional parameters and return structure, but for a simple list tool it is fairly complete.

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 has 5 parameters with only 20% description coverage (date only). The description reinforces required parameters (venue_id, date, party_size) but does not explain optional lat/lng parameters. Given low coverage, more detail would help.

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 'List' and the resource 'available reservation slots' with scope 'specific venue, date, party size'. It distinguishes this tool from siblings like resy_book (booking) and resy_search_venues (searching venues).

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?

It provides guidance on when to use (right before booking) by noting 'Tokens expire quickly; book soon after fetching,' and explains the purpose of tokens. However, it does not explicitly state when not to use or list alternatives.

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