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

Annotations already establish readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely non-structured context: it is free and consumes no browser session, and it enumerates the kinds of content returned (browser choice, sign-in link, method, screens/menus/actions, notes, dedicated tools) 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?

It is dense but front-loaded: the opening names the tool's domain and mechanics, followed by the contents it returns and the call timing. The first sentence is a long comma-chained list that would read better as structured bullets, but every clause carries information rather than 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?

For a two-optional-parameter guidance tool with no output schema, the definition covers what is returned, when to call it, that it costs nothing and opens no session, and how unknown apps are handled. The only gap is any indication of response shape or size, which an agent may want before inlining the guide into context.

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% and both params are documented, so the baseline is 3. The description adds real meaning about how the app parameter is resolved by noting that an app outside Cotlet's catalog still yields the general method, which tells the agent not to restrict inputs to known slugs.

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 states a specific resource and what it delivers: guidance for operating a named web app inside the user's Cloud Browser using Cotlet's browser tools, including which browser and sign-in link to use, step-by-step method, screens/menus/actions, and the app's dedicated tools. This clearly separates it from the cotlet_browser_* action siblings, which do the clicking rather than explain how to.

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" bounds coverage so the agent knows unknown apps are not a dead end. It does not explicitly name alternatives such as cotlet_apps for listing apps or explain when-not to call it, so it falls short of full routing guidance.

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