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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false. The description adds useful behavioral context beyond that: it is free, creates no browser session, works for any web app, and falls back to a general method for apps outside the catalog. It does not describe the exact response shape, but the annotations carry the safety profile.

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 description is compact and front-loads the core purpose before listing guide contents. The first sentence is dense and somewhat run-on, but every clause is relevant to what the guide provides. No filler or repetition.

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?

For a two-parameter, read-only guidance tool with full schema coverage and annotations covering safety, the description is nearly complete: it states when to call, what the guide includes, cost/session behavior, and catalog fallback. The only minor gap is that it does not explicitly describe the return format, though it enumerates the guide's contents.

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%, so the schema already documents both optional parameters, including the default app of ManyChat and the task field. The description reinforces the tool's app-agnostic scope ('works for any web app') but adds no syntax, format, or constraint details beyond what the schema provides. Baseline 3 is appropriate.

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 clearly identifies this as a guidance/reference tool for working in a web app through Cotlet's Cloud Browser, enumerating what the guide covers (browser choice, sign-in link, step-by-step method, screens, menus, actions, notes, dedicated tools). It distinguishes itself from the browser action siblings by framing itself as preparatory guidance and noting 'Free, no browser session,' though it never explicitly says 'this does not click; use cotlet_browser_click for that.'

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 trigger: 'Call it before the first browser step in an app.' It also covers the fallback case for apps outside Cotlet's catalog. It does not explicitly state when not to use it or point to sibling tools like cotlet_apps for discovery, so it stops short of full alternative routing.

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