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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds one genuinely useful fact beyond them: 'Free, no browser session' — telling an agent the call costs nothing and does not open a session. It stops short of describing response size or whether guidance is cached per app.

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 purpose is lead-positioned, but the opening sentence is a long pile-up of clauses listing contents, followed by short routing sentences. Content earns its place, but it could be restructured into shorter, scannable statements.

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?

No output schema exists, so the description usefully previews what the guide contains and when to call it. For a zero-required-parameter, read-only guidance tool this is nearly complete; only the shape/size of the returned guidance is left unstated.

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 are documented in the schema, including the 'ClassPass' default for app. The description adds no format or selection detail for app or task, so the baseline 3 applies.

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 specific verb and resource ('how to work in an app' via Cotlet's browser tools) and enumerates the returned content: browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, and app-specific tools. It implicitly separates itself from cotlet_apps and the browser_* primitives, 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?

'Call it before the first browser step in an app' gives a clear triggering condition, and 'Works for any web app; one outside Cotlet's catalog gets the general method' sets scope. There is no explicit when-not guidance or named alternative (e.g., cotlet_apps for discovery).

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