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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false. The one genuinely additive behavioral fact is 'Free, no browser session' — useful because it tells the agent this costs no browser budget and has no side effects in the user's session. That is real value, but it is a single clause and says nothing about response size or how the guidance is structured.

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?

Content is front-loaded: what it returns, then when to call it, then scope, then cost. The long colon-delimited list in the first sentence is dense and slightly run-on, but every clause carries information and there is no 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 zero-required-parameter guidance tool with no output schema, the description covers what is returned, the timing of the call, applicability to non-catalog apps, and cost. An agent has enough to decide to call it first in a browser workflow; only the shape/volume of the returned guidance is unstated.

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% with both optional parameters documented (app name/slug with a ServiceTrade default, and the user's task in their own words). The description refers to 'the app' but adds no meaning beyond the schema, 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 names the resource (guidance for operating an app in the Cloud Browser) and enumerates the concrete content returned: browser selection, sign-in link, step-by-step method, screens/menus/actions, notes, and dedicated tools. It is clearly distinguishable from the cotlet_browser_* siblings, which perform actions rather than return guidance, though the opening phrase 'How to work in an app by clicking...' is slightly tangled.

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' sets scope for unknown apps. It stops short of naming a sibling alternative to skip it or stating when it is unnecessary (e.g., subsequent steps in the same app), so a 4 rather than 5.

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