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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description adds genuinely new behavioral context: the tool performs no action on its own and its return value is procedural guidance (screens, buttons, fields) rather than live data, which prevents an agent from expecting bookings back.

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 point (returns steps, opens nothing, follow up with browser tools) is front-loaded and useful. However, 'from ChatGPT, Claude or any AI agent' is promotional filler and the closing note about Little Hotelier having no customer API, including a dated audit stamp, is tangential to invoking this tool.

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?

With no parameters, no output schema and full annotation coverage, the definition supplies the essentials: what it returns, that it has no side effects, and which tools to use next. Only the relationship to other Little Hotelier siblings is left implicit.

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 schema takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not introduce any parameter-like expectations that conflict with the empty schema.

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 states the resource (bookings in the user's own Little Hotelier account) and clarifies that the tool actually returns a step-by-step how-to rather than the booking data itself, which corrects a misleading tool name. It remains slightly ambiguous because 'List bookings' implies data retrieval while the body says it returns instructions, so an agent must reconcile the two.

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 a clear follow-up path — do the task with the cotlet_browser_* tools in the Little Hotelier Cloud Browser — which is the practical 'how to act on this' guidance. It does not state when to prefer this over sibling tools such as little_hotelier_get_occupancy_report, nor any when-not-to-use condition other than that it opens nothing by itself.

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