opentable_book_preview

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

Annotations declare readOnlyHint=true, and the description confirms read-only preview behavior. It adds timing context (holds slot ~60-90s) and notes skipping redundant re-lock in book, going beyond 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?

Front-loaded with main purpose, all sentences add value (purpose, required scenarios, alternatives, timing, edge cases). No redundancy despite length.

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?

Covers all critical context: what it surfaces, when mandatory, special cases (Listing, Experience-mandatory), timing, and database region handling. Adequate given no output 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?

Schema coverage is 80%, so baseline is 3. The description adds extra context for experience_id, database_region (with limitation), and auto-resolve for dining_area_id, justifying above baseline.

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 it previews a booking before committing, distinguishes from sibling opentable_book, and specifies the resources surfaced (cancellation policy, payment card, booking_token).

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?

Explicitly says when to use (required for CC-required slots, safe for standard slots) and when not (Listing-type restaurants cannot fetch slot; check bookable first). Also provides guidance for Experience-mandatory slots.

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