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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the bar is lower. The description still adds genuinely useful operational facts: it is 'Free, no browser session', meaning it does not consume a Cloud Browser session, and it must be called before the first browser step. The 'any web app' scope sits loosely against openWorldHint=false, but since the tool only returns internal guidance rather than reaching external entities, this is a mild tension rather than a contradiction.

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?

Every clause carries real information, but the front-loaded sentence is an overstuffed colon list that is hard to parse on first read. The key routing instruction ('Call it before the first browser step') arrives second, after the dense enumeration, weakening the front-loading.

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 explaining what comes back, and it does enumerate the returned content: browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, and dedicated tools. For a zero-required-parameter read-only guide tool, that is close to complete; only the shape/format of the returned guidance is left unspecified.

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?

Schema coverage is 100% and both parameters, including the app-name default of Omio and the task field, are fully documented in the schema. The description does not add format or usage guidance beyond what the schema already says about app and task. Baseline 3 applies since the schema does the heavy lifting.

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 a concrete deliverable: it returns the method for working in an app in the Cloud Browser, including which browser to use, the sign-in link, screens/menus/actions, and any dedicated tools. That clearly separates it from action siblings like cotlet_browser_click or cotlet_browser_navigate. The opening sentence is a 70-word run-on, so the purpose is specific but not crisply stated.

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?

'Call it before the first browser step in an app' gives an explicit trigger condition, and 'Works for any web app; one outside Cotlet's catalog gets the general method' sets the scope boundary. The mention of the app's dedicated tools plus the enumerated Omio actions implicitly points at omio_search_trips / omio_find_the_cheapest_day / omio_start_booking as downstream alternatives, but no explicit 'use X instead when Y' routing is given.

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