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

Annotations already cover the read-only, non-destructive, idempotent, closed-world profile, so the bar is lower. The description adds genuinely new behavioral facts: it is 'Free' and opens 'no browser session,' meaning it costs nothing and leaves no session state — plus it enumerates what the response contains in the absence of an 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 first sentence is a long colon-list that packs several ideas into one run-on clause, and the ordering puts the return contents ahead of the actual call trigger. The content is mostly substantive, but the call-to-action ('Call it before the first browser step') would be stronger front-loaded.

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 output schema, the description correctly takes on the burden of saying what comes back (browser choice, sign-in link, method, screens, notes, dedicated tools). It is nearly complete for a zero-required-parameter guide tool; only the role of the 'task' argument 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 description coverage is 100%, so the baseline is 3. The description echoes the app-slug concept ('which browser to use for this workspace') but never mentions the 'task' parameter, which is the key input that shapes the returned method — that is a missed opportunity rather than a schema failure.

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 makes clear this is a guidance/lookup tool that returns workspace browser choice, sign-in link, step-by-step method, screens/menus/actions and dedicated tools, which distinguishes it from the cotlet_browser_* action siblings. The core verb is implied rather than stated ('How to work in an app...'), so it reads more like a table of contents than a crisp 'returns playbook for app X'.

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,' and states coverage ('Works for any web app; one outside Cotlet's catalog gets the general method'). No explicit when-not or named alternative is given, so the routing to sibling tools is only implied by the list of browser actions.

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