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 adds genuinely new context: it is 'Free, no browser session', meaning it costs nothing and does not touch the live browser, and it previews the returned content (sign-in link, method, screens, notes, dedicated tools). There is no output schema, so a slightly fuller account of the response shape would have raised this further.

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?

Purpose is front-loaded in the first clause, and the operational rule ('Call it before the first browser step') follows immediately. The middle is a long comma-separated inventory of what the guide contains, which is dense but informative; only that enumeration could be tightened without losing signal.

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 zero-required-parameter guidance tool with no output schema, the description does the necessary work: it explains when to call it, that it applies to any web app including ones outside the catalog, that it is free and sessionless, and roughly what information comes back. Nothing critical is missing, though an agent might still wonder how large or structured the returned guidance is.

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% with only two optional parameters, so the schema already carries the semantics; by the baseline rule this is a 3. The description nods at the 'app' parameter indirectly ('which browser to use for this workspace') and at 'task' via 'in an app', but adds no new meaning such as slug format expectations or the Rent Manager default behavior.

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 verb+resource: it retrieves guidance ('how to work in an app', sign-in link, step-by-step method, screens/menus/actions, notes, app-specific tools) for driving a web app in the Cloud Browser. It implicitly separates itself from the cotlet_browser_* siblings by noting it is free and opens no browser session, but it never names those siblings, so the differentiation is inferred rather than explicit.

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?

The when-to-use rule is explicit and actionable: 'Call it before the first browser step in an app.' It also covers the fallback case ('Works for any web app; one outside Cotlet's catalog gets the general method'). It does not say when the guide can be skipped (e.g., mid-workflow lookups) or point to cotlet_apps for discovering the catalog, leaving a small routing gap.

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