resy_book

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

Adds significant behavioral context beyond annotations: composite nature, dry-run preview, confirmation requirement, desired_time handling, and default payment method usage. Annotations mark destructiveHint=true and readOnlyHint=false, and the description aligns with those, adding 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?

The description is front-loaded with the main purpose and logically flows through behaviors. While slightly verbose, every sentence adds value. Could be tightened, but remains clear and well-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?

Given the tool's complexity (9 params, composite, no output schema), the description covers essential behaviors: confirm, desired_time, allow_closest_time, payment method. Lacks detail on lat/lng usage and return format, but the preview description compensates. Sufficient for correct selection and invocation.

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 coverage is 44%, but the description adds meaning for key parameters: confirm (gating), desired_time (24h format and behavior), allow_closest_time (opt-in for auto-booking), and payment_method_id (overrides default). Missing lat/lng explanation, but overall compensates well.

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 'Book a reservation' and explains it's a composite tool with explicit steps (find-slots → get details → book). It distinguishes from sibling tools by detailing the confirm-gated and dry-run behavior, making the purpose unambiguous.

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?

Provides explicit when-to-use guidance: explains require confirmation, how to target a specific time via desired_time, behavior when time unavailable, and the allow_closest_time flag. It also contrasts with other tools like resy_find_slots by noting it does not auto-book different times without explicit opt-in.

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