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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description adds value beyond them by disclosing that the call is free and consumes no browser session, which matters when deciding whether to prepend it before acting.

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 compact and front-loads the trigger sentence about calling it before the first browser step. The middle is a long comma-delimited run-on enumerating guide contents, which is dense but each element carries information the agent needs to know the guide will cover.

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 states the retrieval trigger, the applicable scope (any web app, with a catalog fallback), and the categories of content returned. Nothing essential for correct invocation is missing; only the exact response shape is unspecified, which the absence of an output schema makes forgivable.

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%: both 'app' (name or Cotlet slug, default Thought Industries) and 'task' (the user's own words) are fully documented in the schema. The description adds no syntax, format, or behavioral hints about these parameters, so the schema does all the work and 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 working in a web app via Cotlet's Cloud Browser) and enumerates exactly what the guide returns: which browser to use, the sign-in link, the step-by-step method, screens/menus/actions, notes, and app-specific tools. It is clearly a guidance-retrieval tool rather than an action tool, which separates it from the many cotlet_browser_* siblings, though the opening phrase 'How to work in an app' is a noun phrase rather than a crisp verb.

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 unambiguous trigger point relative to the browser action siblings. It also covers the fallback case explicitly: 'Works for any web app; one outside Cotlet's catalog gets the general method.'

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