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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond that: it is free, opens no browser session, returns workspace-specific browser and sign-in guidance, and falls back to a general method for uncatalogued apps.

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 definition is appropriately sized and front-loads the core purpose, then follows with usage and coverage notes. The first sentence is a long comma-heavy inventory, but every clause contributes useful information, and the short follow-up sentences keep the key constraints visible.

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 two-parameter guide tool with no output schema, the description is substantially complete: it explains what guidance will be returned and what the tool does not do, such as opening a browser session. It does not specify the exact return format, but that gap is minor given the tool's simplicity.

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 app and task parameters are already documented in the input schema. The description adds some meaning by noting that the app may be outside Cotlet's catalog, but it does not clarify how the task parameter shapes the returned guide, 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 a specific resource and function: a guide for working in an app via Cotlet's browser tools, including the browser choice, sign-in link, method, screens, menus, actions, notes, and dedicated tools. It distinguishes itself from the browser_* siblings by telling the agent to call it before the first browser step, though the long inventory makes the purpose slightly less crisp than an ideal 5.

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 a clear when-to-use rule: call before the first browser step in an app. It also explains coverage across any web app, including apps outside Cotlet's catalog that receive the general method. It does not explicitly name alternatives such as cotlet_apps for discovery, but the usage context is strong.

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