resy_list_reservations

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

Annotations already mark the tool as readOnlyHint=true. The description adds value by disclosing that results include resy_token, occasion, special_request, and cancellability, enhancing the agent's understanding of the output without contradicting annotations.

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 two concise sentences. The first sentence states the core purpose, and the second adds parameter guidance and output details. No redundant information, front-loaded and efficient.

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 the tool's simplicity (one optional parameter, no output schema, existing annotations), the description is nearly complete. It explains the action, parameter use, and key output fields. Minor gap: it doesn't explicitly state that it returns the user's own reservations, but that is implied by 'the user's Resy reservations'.

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 0%, so the description bears full responsibility. It explains the 'scope' parameter, its allowed values (upcoming, past, all), and the default behavior, providing semantic meaning beyond the schema's enum list.

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 'List the user's Resy reservations' with a specific verb and resource. It distinguishes from sibling tools like resy_book or resy_cancel, and mentions key output fields (resy_token, occasion, special_request, cancellability) that add specificity.

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 provides clear guidance on the 'scope' parameter: defaults to upcoming, with options to pass 'past' or 'all'. While it doesn't explicitly mention when not to use this tool or suggest alternatives, the context is sufficient for a list operation.

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