resy_add_notify

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

No annotations present, so description fully discloses behavior: Resy emails when a matching slot opens, and notes the 30-day notify window. 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?

Two concise sentences front-loaded with purpose and key constraints, no wasted words.

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 main action and constraints; however, it omits behavior if notification already exists or details on removal (sibling resy_remove_notify exists). Slightly incomplete for a mutation tool.

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 67%; description adds context for time_start and time_end formats (HH:MM, 24h) and confirms the 30-day date constraint, enhancing understanding beyond parameter names and type info.

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?

Description clearly states 'Subscribe to Priority Notify for a venue/date/party size' with a specific verb and resource, and it is distinguished from siblings like resy_book (booking) and resy_list_notify (listing).

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?

Description explains when to use (to get an email when a slot opens) and constrains usage with time window and 30-day date limit, but does not explicitly state when not to use or mention alternatives like resy_book for immediate booking.

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