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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely new behavior: "Free, no browser session," meaning no Cloud Browser session is consumed or required, plus that the app defaults to Skedda. It does not describe output size or freshness of the guidance, which keeps it from a 5. No contradiction with the read-only annotation.

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?

Front-loaded with the verb and what the tool returns, then the trigger, then scope and cost. The closing Skedda action list is useful but reads as a tail; a couple of clauses ("notes, and the app's dedicated tools when Cotlet has them") are dense but still earn their place.

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 carries the return-content burden and does so by enumerating the components of the guidance. Combined with 100% schema coverage and read-only annotations, an agent has enough to call it correctly; only the precise effect of `task` and the guidance's freshness are unaddressed.

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 are documented there, so the baseline applies. The description does add that the `app` scope extends to any web app (with general fallback) and that for Skedda it covers named actions, but it never explains how `task` shapes the returned guidance, leaving that parameter's effect implicit.

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 specific resource (guidance for working in an app via the Cloud Browser with Cotlet's browser tools) and enumerates exactly what comes back: which browser to use, the sign-in link, the step-by-step method, the app's screens/menus/actions, notes, and any dedicated tools. That is clearly distinguishable from the sibling browser_* primitives and skedda_* action tools, since this is the prerequisite orientation call.

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," and states the tool works for any web app, with out-of-catalog apps falling back to a general method. It does not explicitly say when to skip it (e.g., whether it is still needed once skedda_* dedicated tools are already known), leaving some inference about ordering against the dedicated tools.

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