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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them by explicitly saying it 'opens nothing by itself.' It adds real behavioral context beyond the annotations: the return value is procedural guidance (screens, buttons, fields) and execution is delegated to cotlet_browser_* tools, which is exactly what an agent needs to know to chain calls correctly.

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 behavior is front-loaded in the first two clauses, which is good structure. But the trailing 'Resy's official API: Resy has no public API (checked 27 Oct 2026)' is awkwardly phrased and the future-dated stamp adds noise rather than decision-relevant information, and the sentence chains two unrelated ideas around a semicolon.

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?

For a zero-parameter tool with no output schema, the description covers the essentials: what it produces (step-by-step instructions), what it does not do (no action taken), and which tools to use next. The remaining gap is edge-case behavior — what happens when the account has no reservation or several — but that is a modest omission relative to 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?

There are zero parameters, so the baseline is 4 and no schema-driven gap exists. The description does not explain how the tool knows which reservation to cancel despite taking no arguments (presumably inferred from the Cloud Browser session), which is the one semantic question a zero-param design raises.

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 first sentence states a specific verb and resource (cancel a reservation in the user's Resy account), and the second sentence immediately clarifies that the tool actually returns step-by-step instructions rather than performing the cancellation. That clarification is what saves it from being misread, though the name/title alone would suggest a direct action, so an agent must read past the first line to get the true purpose.

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 does route the agent forward: 'then do it with the cotlet_browser_* tools in the user's Resy Cloud Browser,' which is genuine sequencing guidance. However, it never states when to pick this over sibling flows like resy_change_a_reservation or resy_list_reservations, nor any precondition (e.g., needing an existing reservation in the account) before calling.

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