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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the call combines a static profile with live bookable timeslots for a given date/party, which is helpful, but it never states what happens when date_time or party_size are omitted and does not describe how 'live' availability varies.

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 tight sentences that front-load the returned data and defer the required-input note. The 'Requires restaurantId' clause mildly duplicates the schema's required list, but nothing is bloated.

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?

An output schema exists, so return values need not be spelled out, and annotations cover the read-only profile. Still, for a tool that fuses a profile lookup with availability, the description omits the key ambiguity of whether profile data is returned when date_time/party_size are absent, which affects correct 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 description coverage is 0%, so the schema gives no parameter meaning. The description compensates partially: it flags restaurant_id as required and associates date_time/party_size with the timeslot lookup. However, it never gives a date/time format or a party-size range, leaving real gaps for the two optional params.

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 names a concrete resource (OpenTable restaurant profile) and enumerates its contents (location, cuisines, hours, price band, review summary) plus live bookable timeslots, so the agent knows exactly what comes back. It does not explicitly name the sibling tools (opentable_restaurant_menus, opentable_restaurant_reviews, opentable_search) to draw boundaries, though the enumerated fields make the scope reasonably clear.

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 line 'Requires restaurantId' is a useful prerequisite that implies the agent must first obtain an ID (e.g., from opentable_search), but there is no explicit when-to-use guidance and no comparison against the sibling menus/reviews tools. Usage is implied rather than stated.

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