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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value beyond that: it states that the response is procedural (screens, buttons, fields) and that the tool opens nothing by itself, which prevents an agent from assuming a side effect occurred. It does not discuss whether the user's OpenTable session must already be authorized in the Cloud Browser.

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 sentence, and the follow-up action is stated immediately after. Slight waste remains in the vendor name-dropping ('ChatGPT, Claude or any AI agent') and the dated official-API footnote, which is useful context for why the browser path is needed but reads as marginal.

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, read-only helper with no output schema and full annotation coverage, the description covers what it returns and what it deliberately does not do. The one loose end is prerequisite state: it doesn't confirm whether the OpenTable Cloud Browser session must already be logged in for the returned steps to be executable.

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 tool takes no parameters, so there is nothing for the description to disambiguate; the empty schema is self-explanatory. Baseline for a zero-parameter tool is 4.

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 makes clear that this tool does not itself check availability but returns a step-by-step how-to (screens, buttons, fields), which is a crucial clarification over the name/title 'Check availability'. It also implicitly distinguishes itself from the cotlet_browser_* tools that perform the actual actions. It stops short of naming cotlet_app_guide or opentable_search_restaurants_with_open_tables as alternatives, so the sibling boundary is only partial.

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?

It gives an explicit usage flow: get the instructions here, then carry them out with cotlet_browser_* tools in the user's OpenTable Cloud Browser. That tells an agent exactly when to call this and what to do next. It offers no when-not guidance and doesn't say why one would pick this over cotlet_app_guide, but the context is clear enough to act on.

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