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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower; the description still adds useful context that this call is free and opens no browser session, which is a real cost/state signal for an agent deciding whether to prime itself before acting. It does not quantify response size or how the guide is structured, but that is minor here.

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?

Front-loads the core statement and keeps to three sentences, but the second sentence is a long comma list of returned artifacts that is denser than necessary. Still, every element earns its place by describing what the agent will receive.

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 describing returns and does so by enumerating browser selection, sign-in link, method, UI map, notes, and dedicated tools. The only gap is not indicating the format/length of the guide, which matters mildly for context budgeting.

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 the 'app' default (Yardi) and the free-text 'task' already documented in the schema. The description adds only indirect meaning — that the app value drives browser choice and dedicated-tool selection — so it does not materially exceed the schema baseline.

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?

States a concrete resource and its payload: a guide covering which browser/sign-in link to use, the step-by-step method, screens/menus/actions, notes, and any app-specific tools. This is immediately distinguishable from the cotlet_browser_* action siblings, which perform clicks rather than return guidance.

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 and ordering rule — "Call it before the first browser step in an app" — which tells the agent exactly where this sits relative to cotlet_browser_open/navigate. It also covers scope (any web app; non-catalog apps fall back to the general method) but states no when-not-to-use or re-call condition.

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