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 operational facts beyond them: that the call is free and opens no browser session, which matters for an agent deciding whether to probe it first. It does not describe the shape of the returned guidance.

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 intent is front-loaded, but the opening sentence is a dense run-on whose colon-list mixes distinct concepts ('notes' is especially vague) and is harder to parse than a short enumerated structure would be. The two trailing sentences are tight and directive, which partially offsets the lead sentence.

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 full annotation coverage, the description supplies everything an agent needs: when to call it, what it returns at a high level, its scope limits, and its zero-cost/no-session behavior. Nothing required for correct invocation is missing.

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 the 'app' and 'task' parameters are already documented in structured form, setting the baseline at 3. The description adds nothing about how the app name or slug should be supplied, or how the task wording shapes the returned method, so it neither helps nor compensates.

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 framing ('How to work in an app ... with Cotlet's browser tools') and enumerates what the guide contains (browser choice, sign-in link, step-by-step method, screens, menus, actions, dedicated tools). It is clearly distinguishable from the sibling cotlet_browser_* action tools, though the long colon-list makes the core purpose slower to grasp than it should be.

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 explicit timing guidance ('Call it before the first browser step in an app') and states the coverage boundary ('Works for any web app; one outside Cotlet's catalog gets the general method'). It never names a sibling alternative to avoid, so it falls short of a 5, but the when-to-use rule is unambiguous.

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