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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: it is free and opens no browser session, and non-catalog apps degrade to the general method. However, it says nothing about the shape or size of the returned guidance, which matters for a documentation-style tool.

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 content is dense and every clause is informative, but the first sentence is a long comma-chained inventory that buries the actual action. The most important instruction, 'Call it before the first browser step in an app,' arrives only in sentence two, so the description is not 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 carries the burden of explaining what comes back, and it does so exhaustively: browser choice, sign-in link, method, screens, menus, actions, notes, and dedicated tools. Combined with the usage trigger and the no-session cost note, an agent has everything needed to decide to call it and to interpret the result.

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 parameters are already described in the schema, including the 'Default: Acuity Scheduling' behavior and the free-text task. The description adds no extra meaning about how app/task influence the returned guidance (e.g. whether task narrows the method), 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 states the resource precisely — a pre-flight guide covering browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, and any dedicated app tools — and names the domain ('Cloud Browser with Cotlet's browser tools'). It is distinguishable from the browser_* siblings because it explicitly returns knowledge rather than performing a browser action, though the delivering verb ('returns guidance for') is implied rather than stated.

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 a scope rule ('Works for any web app; one outside Cotlet's catalog gets the general method'), which is exactly the when-to-use guidance an agent needs. It does not explicitly name a sibling alternative to use instead, which keeps it 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.