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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description still adds non-obvious behavior: it is free and starts no browser session, which matters for an agent deciding whether to call it speculatively. It does not describe the shape or length of the returned guidance.

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 run-on list of deliverables that is harder to parse than needed, and the call-timing instruction arrives second rather than being front-loaded. All the content earns its place, but the packaging could be tightened into shorter, ordered sentences.

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 two optional parameters, no output schema, and rich annotations, the description covers what the tool returns and when to call it. The only gap is not knowing the return format or size, which is minor for a documentation-retrieval tool.

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 documented there, including the Virtuagym default. The description only adds the implication that the app value may fall outside Cotlet's catalog, which is a marginal semantic gain rather than real parameter guidance.

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?

States a specific verb and resource: it retrieves instructions for working in a web app via the Cloud Browser, and enumerates the contents (which browser, sign-in link, step-by-step method, screens/menus/actions, notes, app-specific tools). That inventory distinguishes it clearly from the cotlet_browser_* action siblings, which perform steps rather than explain them.

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. No when-not-to-call case is stated, but there is no real competing tool for this purpose.

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