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

Annotations already declare readOnlyHint, non-destructive, idempotent and non-open-world, so the description is not the sole safety carrier. It still adds real value beyond them: it says nothing is opened by the tool itself, that the return value is a step-by-step walkthrough (screens, buttons, fields), and that Little Hotelier has no public API for its own customers (with a check date) — the reason the browser tools are needed.

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?

Purpose is front-loaded in the first clause, followed by return behavior, then the follow-up tools, then the API rationale. It is a dense run-on construction with semicolons and a parenthetical date, but every clause carries information an agent needs.

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 annotations covering the safety profile, the description supplies what is otherwise missing: the shape of the response (step-by-step instructions), the fact that nothing is executed, and the hand-off to browser tools. Minor gaps remain around preconditions (e.g., whether the user must already be signed in to the Cloud Browser).

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 and the schema is fully closed, so there is nothing for the description to disambiguate. Baseline 4 applies.

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 gives a specific verb and resource (update rates in the user's own Little Hotelier account) and immediately clarifies that the tool itself returns step-by-step instructions rather than performing the change. That clarification resolves the mismatch between the 'update' name and the guide-style behavior. It does not explicitly contrast with lookalike siblings such as little_hotelier_update_availability.

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 states the context for use (updating rates in Little Hotelier from an AI agent) and routes the agent to the follow-up mechanism: cotlet_browser_* tools in the user's Cloud Browser. There is no explicit when-not-to-use guidance or differentiation from the other little_hotelier_* mutation/query siblings.

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