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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description adds two pieces of real behavioral context: 'Free, no browser session' (no session opened, no cost) and the fact that the result degrades gracefully to a general method for uncatalogued apps. Return format specifics are left implicit, which is the only 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?

The content is relevant, but the first sentence is a single sprawling enumeration and the most actionable instruction ('Call it before the first browser step in an app') arrives in the middle rather than up front. The trailing Pic-Time action list is useful for routing but reads as padding for non-Pic-Time users.

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?

There is no output schema, and the description does explain what the response contains (browser choice, sign-in link, step method, screens/menus/actions, notes, dedicated tools), which covers the main thing an agent needs. It omits whether the returned guidance is scoped to the supplied task or always full-app, a minor remaining gap for a 2-param read-only tool.

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 optional parameters are already documented in the schema, including the Pic-Time default, so the description adds little beyond it. Mentioning the Pic-Time action set gives some sense of what the 'app' parameter unlocks, but it does not clarify the 'task' parameter's role in shaping the returned method. 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 opening clause and the enumeration ('which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools') make clear this is a guide/instruction-retrieval tool rather than a browser action, which separates it from the cotlet_browser_* siblings. It stops short of a crisp one-line statement of purpose because the enumeration is buried in a long compound sentence.

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' explains coverage boundaries. It never states when not to call it (e.g. whether it should be re-called per step or per app), leaving one inference to the agent.

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