opentable_find_slots

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

Annotations already declare readOnlyHint=true, indicating safety. The description adds significant behavioral context: token expiration, direct use of slot_hash in booking, the limitation regarding database_region, and the browser tab workaround. This goes well beyond the annotation.

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 packed with useful information but is slightly lengthy. It front-loads the core purpose and is well-structured with parenthetical clarifications. Could be trimmed slightly without losing key details.

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 complexity (5 parameters, no output schema), the description covers behavioral and error-handling aspects well. However, it does not fully specify the response structure beyond mentioning reservation_token, attributes, and type. More detail on the return format would improve completeness.

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?

The description adds meaning for the database_region parameter, explaining its necessity and limitation. For other parameters, the schema already provides descriptions, but the description clarifies that 'time' is an anchor time and slots are relative to it, adding value.

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 the tool lists available reservation slots for a specific restaurant, date, and party size. It differentiates from siblings by explicitly mentioning the returned reservation_token and its use with opentable_book, as well as slot attributes and types.

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 explicit guidance on when to use the tool (before booking), mentions token expiration, and gives a workaround for a specific error. However, it does not explicitly contrast with alternatives like opentable_book_preview or state when not to use it.

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