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 context the annotations cannot: 'Free, no browser session,' which tells the agent this call does not consume or open the Cloud Browser and therefore has no cost or state side effects. It does not describe output size or truncation behavior for apps with many screens, a minor gap.

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?

Purpose is front-loaded in the opening clause, which is good. However, the first sentence is a long comma-chained enumeration of return contents that takes effort to parse, and 'notes' plus 'the app's dedicated tools when Cotlet has them' are vague entries. A tighter list would convey the same scope with less reading cost.

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 usefully enumerates what comes back (browser selection, sign-in link, method, screens, menus, actions, app-specific tools). Both parameters are optional and schema-documented, and the call has no side effects. It is only slightly short of complete because it does not indicate the shape or length of the returned guidance.

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 already documented in the schema, including the default of Absorb LMS and the free-form task wording. The description's phrase 'which browser to use for this workspace' hints that the app parameter drives workspace-specific output, but adds no format or disambiguation detail beyond the schema. 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 verb: it returns guidance on how to operate an app through Cotlet's browser tools. It enumerates the content (browser choice, sign-in link, step-by-step method, screens, menus, actions, notes, dedicated tools), which distinguishes it from the cotlet_browser_* action siblings as a read-a-guide tool. It is dense but the identity of the tool is unmistakable.

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?

Explicit sequencing guidance is given: 'Call it before the first browser step in an app,' which tells the agent when in the workflow it belongs. The edge case is also handled: 'Works for any web app; one outside Cotlet's catalog gets the general method.' What is missing is a direct contrast with cotlet_apps (catalog lookup) versus this tool, but no alternatives are required here.

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