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 two genuinely useful facts beyond that: "Free, no browser session", which tells the agent this call consumes no browser session or credits, and that the scope is pre-action planning. It does not say whether the answer is cached or how large it is.

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 is front-loaded in the first sentence, followed by two compact sentences giving timing and scope. The middle enumeration is list-like and dense but every item describes a distinct part of the returned guidance, so little is wasted.

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?

This is a simple two-parameter read tool with no output schema, so the description must convey what comes back, and it does by listing the sections of the guide. The only gap is the absence of any indication of answer length or of what happens when the app name is unrecognized.

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%, including the LawnBoss default, so the schema already carries both parameters. The description adds no meaning for app or task beyond noting that uncatalogued apps fall back to a general method. Baseline 3 applies when the schema does the heavy lifting.

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 a concrete deliverable: guidance for operating a web app through Cotlet's browser tools, enumerating the contents (browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, dedicated tools). That distinguishes it from the cotlet_browser_* action siblings, though it never names one explicitly as the alternative for actually clicking.

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 in the workflow, and "Works for any web app; one outside Cotlet's catalog gets the general method" sets scope expectations. It lacks an explicit when-not condition or a named sibling to skip in favor of this one.

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