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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower, and the description still adds useful facts: it is free, consumes no browser session, works for any web app, and degrades to a general method for uncatalogued apps. It also enumerates the concrete content returned (browser choice, sign-in link, method, screens, notes, dedicated tools), which is real behavioral context.

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 purpose and the 'call it before the first browser step' instruction are front-loaded, which is good, but the opening sentence is a long run-on enumeration that packs six content categories into one clause chain. It is informative rather than padded, yet a bulleted or shorter phrasing would be easier to parse.

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?

There is no output schema, and the description compensates by spelling out what the guide returns: browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, and app-specific tools. For a two-optional-parameter informational tool this is nearly complete; only the absence of any length or scope caveat on the returned guidance keeps it from a 5.

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 (app, task) are fully documented in the schema, so the baseline of 3 applies. The description adds only the Portrait Care default and the action list for that app, which hints at how 'app' and 'task' are consumed but adds no format or matching guidance beyond the schema.

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: guidance on operating a named web app through Cotlet's browser tools, including which browser to use, the sign-in link, the step-by-step method, and app screens/menus/actions. It is clearly distinguishable from the browser_* action siblings, though the opening phrase 'How to work in an app' is softer than an explicit verb like 'returns the playbook for'.

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', which sequences it ahead of cotlet_browser_navigate/click, and it states the fallback for apps outside Cotlet's catalog. It does not name a competing alternative tool to avoid, so it stops short of full when/when-not coverage.

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