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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world, so the safety profile is covered. The description adds genuinely new behavior: 'Free, no browser session,' and a fallback path for apps outside the catalog. It says nothing about response size or what the agent should do if the returned steps fail.

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?

It is one long run-on sentence enumerating contents with commas, which makes it slower to parse than a short purpose line followed by a timing line. Little is wasted, but the structure is not front-loaded cleanly.

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 burden of saying what comes back, and it does enumerate the returned content plus the free/no-session behavior. Missing only edge details such as what happens for an unknown app slug or a task mismatch.

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%, with both app and task documented in the schema, so the baseline applies. The only added meaning is that app tolerates names outside Cotlet's catalog, which is useful but marginal.

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 clear resource: a per-app how-to guide covering browser choice, sign-in link, step-by-step method, screens/menus/actions, and app-specific tools. This clearly separates it from the cotlet_browser_* action tools, though the opening clause is dense enough that the core 'returns guidance, performs no actions' point arrives late.

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?

Gives an explicit trigger ('Call it before the first browser step in an app') and a coverage rule ('Works for any web app; one outside Cotlet's catalog gets the general method'). It does not say whether to call once per app or per task, nor name an alternative to use instead, so it stops short of full routing guidance.

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