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 adds two genuinely new behavioral facts — it is free and consumes no browser session — but says nothing about response size, latency, or what happens when the app is unknown beyond 'general method'. Useful additions, still thin.

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?

No sentence is pure filler, but the opening sentence is a long comma-chained enumeration that delays the actual point, and the critical trigger instruction ('Call it before the first browser step') is pushed to the end. Front-loading the trigger and trimming the list would improve scannability considerably.

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 enumerates what comes back (browser choice, sign-in link, method, screens, menus, actions, notes, dedicated tools), which is the essential information for a two-parameter guide tool. Minor gaps remain around unknown-app behavior and result size, but nothing blocks a correct call.

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 description coverage is 100%, including the 'Default: Mailjet' note on app, so the baseline is 3. The description alludes to the app parameter ('which browser to use for this workspace') but never explains the `task` parameter's role or how it shapes the returned method, leaving no added meaning over 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 names a concrete deliverable — a per-app playbook containing workspace browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, and any dedicated tools — which is clearly distinguishable from the cotlet_browser_* action siblings. The verb is somewhat buried in a long enumerative first sentence, so the purpose is clear but not as crisply stated as it could be.

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 condition, and "Works for any web app; one outside Cotlet's catalog gets the general method" covers the fallback case. It stops short of naming specific alternatives (e.g. cotlet_apps for discovery vs. this for procedure), so the routing against siblings is only implied.

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