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

Beyond the readOnly/idempotent/non-destructive annotations, the description adds that the call is free and opens no browser session, and it previews the shape of the returned guidance. That is meaningful operational context an agent would not get from the annotations alone, though the exact return structure is only loosely sketched rather than fully specified.

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 essential cue — when to call it — is front-loaded and followed by a compact enumeration of what it returns. The opening sentence is long and list-heavy, and the trailing AppFlowy action inventory is somewhat dense, but every clause carries information relevant to deciding whether to call.

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 correctly takes on the burden of describing what comes back, and it does so at a useful level of granularity. For a zero-required-parameter, read-only lookup with full schema coverage, nothing an agent needs in order to call it correctly is absent.

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%, so the baseline would be 3; the description earns above that by clarifying that 'app' accepts any web app and that apps outside Cotlet's catalog fall back to a general method rather than failing. The 'task' parameter's role is left entirely to the schema, which limits it to a 4.

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 a specific verb and resource (retrieve a how-to guide for working in an app inside the 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 any dedicated app tools. It is clearly distinguishable from the sibling browser_* action tools because it is the pre-flight briefing rather than a browser action.

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?

Timing is stated explicitly: 'Call it before the first browser step in an app', and coverage is bounded ('Works for any web app; one outside Cotlet's catalog gets the general method'). What is missing is a negative case — nothing says when this call can be skipped, e.g. if a guide was already retrieved in the session.

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