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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description stays consistent with them by stating it opens nothing by itself. It adds genuinely non-obvious behavior beyond the annotations: the return is a procedural walkthrough of screens/buttons/fields, not contact data, and execution belongs to the browser tools. It does not describe the shape or length of that returned guide (no output schema exists), which keeps it from a 5.

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 core disclosure (returns steps, opens nothing, then use browser tools) is front-loaded and efficient. However, "from ChatGPT, Claude or any AI agent" is promotional filler that does not help selection or invocation, and the "checked 23 Oct 2026" date stamp is incidental. Two of the sentences carry non-essential wording.

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?

For a zero-parameter guidance tool with full annotation coverage and no output schema, the description supplies what the agent needs: it is instructional, it is side-effect free, and it hands off to browser tools. The remaining gap is the handoff mechanics — whether cotlet_browser_open or a Mautic Cloud Browser session must exist before those follow-up calls — which is left implicit.

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 and the baseline of 4 applies. The description correctly implies no inputs are needed. No additional parameter-level meaning was possible or required.

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 explicitly states the tool "Returns how to do it in Mautic step by step (screens, buttons, fields) and opens nothing by itself," which corrects the impression given by the name/title that it fetches contact data. It also names the follow-up surface (cotlet_browser_* in the Mautic Cloud Browser), so the agent can tell it apart from a real listing tool. It stops short of differentiating against in-catalog guide siblings, so it lands just below a 5.

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?

Clear sequencing is given: call this to get step-by-step instructions, then execute with the cotlet_browser_* tools — that is real when-to-use guidance. The caveat "opens nothing by itself" steers the agent away from expecting side effects. There is no explicit when-not guidance and no prerequisites (e.g. whether a browser session must first be opened) are stated.

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