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

Adds real context beyond the annotations: the browser is a real Chrome where the user is already signed in, the URL reuses the site's existing tab or opens a new one so the user's tabs survive, and the tool returns the in-view elements and text with the same numbering used later. Annotations already cover safety (readOnly=true, openWorld=true, destructive=false), and the description usefully adds environment, side effects, and return shape; session lifetime and how to close it are left to cotlet_browser_close.

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 key facts (call first, tab reuse, returns the page contents) are front-loaded and earn their place. The closing list of AppFlowy actions (List workspaces, Read page tree, ...) is tangential to opening a browser and duplicates the appflowy_* sibling tools, which dilutes the message.

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 two-parameter, no-output-schema tool with full annotations, the description covers environment, tab placement, ordering, and what is returned. Gaps are minor: no guidance on authentication failures, session persistence, or when to close the browser.

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 tricky optional `app` slug with the cotlet_app_guide pointer. The description adds tab-targeting behavior for `url` but says nothing about the `app` parameter, so it remains at the baseline for a fully-described schema.

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?

States a specific verb and resource: starts the user's Cloud Browser (a real Chrome on Cotlet with the user signed in) and opens `url`. The ordering instruction 'Call it first' implicitly separates it from cotlet_browser_navigate and the other browser_* action tools, though it never names that sibling outright.

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 first' gives an explicit prerequisite for the rest of the browser workflow, and the schema note on `app` explains the only exception (an app's own Cloud Browser named in cotlet_app_guide). No explicit when-not-to-use statement or named alternative, so it stops short of a 5.

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