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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new facts beyond that: 'Free, no browser session' tells the agent this costs nothing and consumes no browser session, which materially affects sequencing decisions. It stops short of describing output shape or length.

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 and trigger are front-loaded in the first two sentences, and the trailing catalog of Constant Contact actions is concrete matching signal rather than filler. It is still dense and list-heavy, and the covered-topics inventory ('screens, menus and actions, notes') could be compressed without losing meaning.

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 explaining what comes back, and it does: browser choice, sign-in link, step-by-step method, UI map, notes, and pointers to dedicated tools. It also covers cost, session impact, and catalog-vs-generic behavior — everything needed to call this correctly before starting an app workflow.

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%, so both parameters are already documented, and the description adds little about them beyond implying 'app' selects the workspace/browser/sign-in link. The 'task' parameter — arguably the most important, since it determines which of the listed Constant Contact actions is relevant — is never discussed in the description. 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 a specific resource and role: a pre-flight how-to guide covering 'which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions'. That clearly separates it from the action siblings (cotlet_browser_click, constant_contact_create_list), which perform work rather than explain it. It loses a point only because the purpose is buried in a long comma-separated inventory rather than stated in one crisp 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' sets scope. What's missing is a named alternative for discovery (e.g., pointing at cotlet_apps to resolve an app name or slug) and any statement about when re-calling is unnecessary.

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