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

Adds substantial context beyond the readOnly/idempotent annotations: the tool 'opens nothing by itself', so the agent knows no browser session is launched and no state changes occur until it drives cotlet_browser_* itself. It also justifies the approach with the absence of a traveler-account API, which explains why a screen-by-screen guide is returned instead of data.

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?

Three compact sentences, front-loaded with the scope and the key non-obvious fact (no browser opened by itself). The 'from ChatGPT, Claude or any AI agent' clause and the 'official API' note are slightly promotional but do carry justification for the tool's design.

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 output schema, the description carries the burden of describing the return value and does so ('screens, buttons, fields'). It also names the tools to use afterwards. It falls short only on the surrounding workflow, such as what the agent should do if the browser session is not already open.

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 zero parameters, so there is nothing for the description to disambiguate; baseline applies. The description correctly signals a parameterless call by describing a fixed step-by-step output.

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?

States a specific verb and resource (list bookings in the user's own Klook account) and immediately clarifies that the tool returns step-by-step instructions rather than the bookings themselves. The name/behavior mismatch ('list' vs. 'returns how to do it') is disclosed, but the opening sentence still reads as though it lists bookings directly before the correction lands.

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?

Gives clear downstream guidance: after this call, perform the navigation with the cotlet_browser_* tools in the user's Klook Cloud Browser. However, it never says when to prefer this over siblings like klook_search_activities or klook_book_activity, and gives no explicit exclusions or prerequisites for starting the flow.

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