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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds genuinely new behavioral facts not in the annotations: the call is free and opens no browser session. Beyond that it does not say how large or structured the returned guidance is.

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?

Front-loaded with the tool's purpose, then a single call-timing sentence and a scope/cost line. The opening sentence is long and list-heavy and the closing 'Free, no browser session' is terse relative to the rest, but almost nothing is wasted.

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 no-side-effect guidance tool with no output schema, the description covers what comes back, when to call it, how unknown apps are handled, and that it costs nothing. Missing only the shape/size of the returned guide, a minor gap given no output schema exists.

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 description coverage is 100% and both parameters (app, task) are documented there, including the Freshchat default, so baseline 3 applies. The description only implies the app parameter is free-form ('any web app') and adds nothing about how task changes the guidance returned.

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?

Specific: it states the tool returns a guide for working in a web app through Cotlet's Cloud Browser, and enumerates the content (which browser, sign-in link, step-by-step method, screens/menus/actions, notes, dedicated tools). The phrase 'Call it before the first browser step in an app' cleanly separates it from the cotlet_browser_* action siblings.

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 explicit timing ('before the first browser step in an app') and a fallback rule ('Works for any web app; one outside Cotlet's catalog gets the general method'), plus points at dedicated tools when they exist. No explicit when-not-to-use or cost trade-off against calling the browser tools directly, so not a full 5.

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