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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description reinforces this with the explicit "opens nothing by itself," which is the single most important behavioral fact for an agent that might otherwise assume a write occurred. It also discloses the return content (screens, buttons, fields), which matters since there is no output schema. It stops short of saying anything about rate limits or failure modes, but that is a minor gap against annotations that already cover the safety profile.

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 critical fact (it does not create anything) is buried mid-sentence rather than front-loaded, and the trailing sentence about Constant Contact's v3 REST API and beta MCP server explains nothing about invoking this tool — it is pure distractor text, complete with an oddly specified "checked 22 Oct 2026" date. The structure forces the agent to parse past irrelevant vendor background to find the operative instruction.

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 zero parameters and no output schema, the description does the necessary work of explaining what comes back (step-by-step screens/buttons/fields) and what to do next (cotlet_browser_* tools). However, given that the tool name promises a creation action, the description should state unambiguously and early that no list is actually created and that the agent must follow up with browser tools — instead this key fact is diluted by the API trivia.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. The baseline applies and no misleading parameter guidance is present.

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 sentence says "Create list in the user's own Constant Contact account," which names a verb and resource, but the very next clause reverses it: the tool "opens nothing by itself" and only "Returns how to do it in Constant Contact step by step." The real function is a how-to/guide generator, and an agent must read two conflicting sentences to work that out, so the actual purpose is only inferable rather than stated cleanly.

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?

It does provide a sequencing instruction: use this first to get the steps, "then do it with the cotlet_browser_* tools in the user's Constant Contact Cloud Browser." That is genuine when-to-use context, but there is no guidance on when not to use it versus the sibling API-based tools like constant_contact_add_contacts_to_list, and no prerequisites or conditions are given.

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