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 behavior: the call is free and starts no browser session, and it discloses the shape of what comes back (method, screens, notes, dedicated tools) — useful because there is no output schema.

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 front-loaded and the 'Free, no browser session' fragment is a well-placed, high-value trailing note. The middle sentence is a dense list-in-a-sentence ('the method step by step, the app's screens, menus and actions, notes, and…') that could be split for scannability, but there is no filler.

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 no required parameters and no output schema, the description does list the sections an agent can expect, which is the right compensation. It stops short of saying how the guidance is returned (free text to read vs. structured steps) or what an agent should do if the returned method is ambiguous, leaving a modest gap for a tool whose whole value is the content of its response.

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%: both `app` (name or slug, with an iSpring Learn default) and `task` (the user's goal in their words) are already documented in the schema. The description adds only indirect context — that the guide is tailored to the workspace's browser and sign-in link — without explaining how `task` changes the returned guidance, 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 names the resource (guidance for working inside a specific web app via the Cloud Browser) and enumerates what the guide contains: browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, and dedicated tools. It reads as a knowledge-retrieval tool rather than an action, which clearly separates it from the cotlet_browser_* siblings, though the leading 'How to work in an app' phrasing is softer than a concrete verb.

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 an explicit trigger point, and 'Works for any web app; one outside Cotlet's catalog gets the general method' sets scope for uncatalogued apps. The main gap is that it does not point to cotlet_apps for discovering a valid app name/slug when the user hasn't named one.

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