resy_cancel

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

The description reveals the dry-run preview behavior and cancellation fee disclosure, which goes beyond the annotations (destructiveHint: true) by detailing what happens in preview mode and what information is returned.

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 sentences: the first states the core function and identifier source, the second explains the critical confirm gating. No unnecessary words, effectively front-loaded.

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?

No output schema exists, but the description adequately covers return info (preview details for dry-run, and implies success for actual cancellation). Could briefly mention successful cancellation confirmation, but completeness is high given the tool's simplicity.

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?

Despite 100% schema coverage, the description adds meaning: it specifies the resy_token format ('rr://...') and clarifies the confirm parameter's role as a gating mechanism, enhancing the schema descriptions.

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 action ('Cancel') and the resource ('Resy reservation') using the resy_token identifier. It differentiates from sibling tools like resy_book and resy_list_reservations by focusing solely on cancellation.

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 explains the confirm-gated behavior: without confirm:true it returns a preview; with confirm:true it executes cancellation. This tells the agent exactly when and how to use the tool, including the dry-run preview content.

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