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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description earns credit for adding cost and side-effect context: 'Free, no browser session,' which tells the agent this call consumes no session budget. It also previews the return content (method, screens, menus, actions, notes), valuable given there is no output schema. Minor gap: it does not say what happens when the app is unknown beyond 'gets the general method.'

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 enumerated deliverables are front-loaded, followed by the call timing and scope notes. Dense but every clause carries information; the only mild redundancy is restating the 'works for any web app' fallback alongside the catalog mention.

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?

For a read-only guidance tool with no output schema, the description does the heavy lifting by listing what the agent will receive and when to call it, plus the out-of-catalog fallback. It is nearly complete; the only thing left implicit is whether an unrecognized app name errors or degrades to the general method.

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% and both parameters (app, task) are documented in the schema, including the Tekmetric default. The description mentions neither parameter nor how 'task' shapes the returned guidance, so it adds no meaning 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 names the resource (guidance on working in an app via Cotlet's Cloud Browser) and enumerates the concrete contents: which browser for the workspace, sign-in link, step-by-step method, screens/menus/actions, notes, and dedicated tools. That clearly separates it from the cotlet_browser_* action siblings, which perform browser steps rather than explain them. It stops short of naming a specific sibling as an alternative, so it lands at 4 rather than 5.

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 point, and 'Works for any web app; one outside Cotlet's catalog gets the general method' defines scope and fallback behavior. There is no explicit when-not-to-use statement, but the timing cue is strong enough that an agent knows exactly when this fires.

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