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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond them: the call is free and opens no browser session, which tells an agent it can invoke it pre-emptively without consuming workspace resources. It does not describe the shape of the returned guidance, though that is partially covered by the content list.

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 trigger sentence is front-loaded and the contents are packed into a single dense clause with no filler. The phrasing 'How to work in an app by clicking in the user's Cloud Browser' is slightly awkward and echoes the title, but no sentence 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?

With only two optional parameters, no output schema, and annotations carrying the safety profile, this tool is simple enough that the description is nearly sufficient. Listing what the guide contains effectively substitutes for a missing output schema; only the 'task' parameter's effect on the result is left unaddressed.

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 both parameters are already documented, including the default of SmugMug for 'app'. The description only marginally enriches this by implying 'app' accepts any web app, not just catalog entries ('one outside Cotlet's catalog gets the general method'), and says nothing about the 'task' parameter's role in tailoring the guide. 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 states a specific resource (guidance for working in a named web app inside the Cloud Browser) and enumerates its contents: browser choice and sign-in link, step-by-step method, screens/menus/actions, notes, and any dedicated Cotlet tools. This clearly separates it from the browser_* action siblings, which perform clicks and navigation rather than returning a playbook.

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' — plus a fallback rule: apps outside Cotlet's catalog still get the general method. It stops short of naming a specific sibling (e.g., cotlet_apps for discovering valid app names) or stating when the guide can be skipped, so it is strong but not exhaustive.

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