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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), it adds two facts the agent cannot get from structured data: it is free and consumes no browser session. That cost/side-effect disclosure is genuinely useful for planning. It stops short of describing response shape or size limits.

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 call-to-action ('Call it before the first browser step in an app') is placed after the capability list rather than first, but the whole thing is four sentences with no filler. The opening sentence is a comma-heavy enumeration that takes effort to parse, which is the main structural weakness.

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 correctly carries the burden of describing what comes back, and it does so item by item. Combined with the cost note and the fallback behavior for uncatalogued apps, an agent has enough to decide to call it and what to expect; only the exact form/structure of the returned guide 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 carry their own descriptions (including the FitBudd default), so the baseline of 3 applies. The description adds one real insight — any app name is accepted and unknown ones fall back to the general method — but adds nothing about the 'task' parameter, such as how detail of the returned guide scales with it.

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 uses a clear framing — it is the guide/instruction lookup for operating an app in Cotlet's Cloud Browser — and enumerates the payload an agent will receive (browser choice, sign-in link, step-by-step method, screens, menus, actions, notes, dedicated tools). It is distinguishable from the cotlet_browser_* action tools, which actually perform the clicking, though it never names a sibling explicitly.

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 trigger: 'Call it before the first browser step in an app.' It also sets scope broad enough to be actionable — 'Works for any web app; one outside Cotlet's catalog gets the general method' — which tells the agent it need not pre-check the catalog. No explicit when-not-to-use case is stated, so it falls short of a 5.

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