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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds context annotations cannot: the response always includes booked=false and mode="deeplink", no inventory is held, and a fallback phone number appears for venues without a platform. Nothing contradicts the readOnlyHint.

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 core warning is front-loaded and every sentence is functional, though the platform enumeration (OpenTable, Resy, Tock, SevenRooms, Square and others) and heavy all-caps emphasis add minor noise to an otherwise tight definition.

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?

There is no output schema, and the description compensates by naming the exact response fields (booked: false, mode: "deeplink") plus the no-platform fallback. An agent has everything needed to call it and to interpret the result safely.

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 100%, so date/time/party/place_id formats are already documented in the schema. The description only restates that these values are pre-filled into the link, adding no format or constraint detail beyond structured data — the baseline 3 for full coverage.

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 states precisely what the tool produces — a pre-filled booking page (deeplink) for one place — and immediately distinguishes it from a reservation-making tool. An agent can tell exactly what it gets back versus what it would get from a real booking action.

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 gives explicit when-to-use framing, explicit when-not-to (do not present as a confirmation, do not claim a table is held), and an alternative path when no booking platform exists (offer the returned phone number instead of implying the venue can't be visited).

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