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

The annotations already declare this a safe read-only, idempotent, non-destructive operation, so the bar is lower. The description still adds real behavioral value: "Free, no browser session" tells the agent calling it costs nothing and consumes no browser slot, and the catalog/fallback note explains how the response differs for unknown apps.

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 in the first clause and the operative instruction ("Call it before the first browser step") follows the content list. The opening sentence is a long laundry list of what the guide contains, which is slightly dense but each item tells the agent something it would otherwise have to discover by calling.

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 takes on describing what comes back, and it does so reasonably: browser choice, sign-in link, method, screens/menus/actions, plus the existence of app-specific tools. It does not describe the response shape or how long the guide is, but for a documentation-retrieval tool on a two-parameter read-only call, the essentials are covered.

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%, with both optional parameters documented in the schema including the FieldRoutes default, so the schema does the heavy lifting. The description adds no guidance on how to phrase the app name or task, 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 clearly states the resource: a guide for working in an app through the Cloud Browser with Cotlet's browser tools, and enumerates what the guide covers (browser choice, sign-in link, step-by-step method, screens, menus, actions, notes, dedicated tools). It implicitly distinguishes itself from the many cotlet_browser_* siblings by positioning itself as the thing to consult first, though it never names a sibling explicitly.

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 a concrete, actionable trigger, and "Works for any web app; one outside Cotlet's catalog gets the general method" sets expectations for coverage. It lacks an explicit when-not or a named alternative (e.g., cotlet_apps for listing apps), so it falls short of a full 5.

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