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

Beyond the annotations, it discloses the key non-obvious trait: the tool performs no action itself and returns a described guide (screens, buttons, fields), which matches readOnlyHint=true and destructiveHint=false with no contradiction. It also flags the Pro-plan/API caveat. Minor remaining gap is that it doesn't say how the guide is structured or bounded in 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?

The behavior-changing information (returns a guide, opens nothing, then use cotlet_browser_*) is front-loaded, but "from ChatGPT, Claude or any AI agent" is filler and the trailing API-plan sentence with a dated check reads as an aside rather than actionable instruction. Tightening to two sentences would lose nothing.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it does: a step-by-step walkthrough of screens, buttons and fields, plus the hand-off to browser tools. Complete enough to call correctly, though it could state whether the guide is ManyChat-version-specific.

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 no parameter meaning to add and the baseline of 4 applies. Nothing in the description misleads about inputs.

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 lead sentence promises a data fetch ("Get contact profile"), but the body reveals the tool actually returns step-by-step instructions for doing it manually and "opens nothing by itself." The tension between the name/lead verb and the real behavior leaves an agent uncertain whether the return value is a profile payload or a guide, even though the guide nature is eventually stated.

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 explicitly routes follow-up work to the cotlet_browser_* tools in the ManyChat Cloud Browser and notes that the official API exists but is Pro-only and narrow, which is real guidance about when to prefer this path. It stops short of naming a specific sibling alternative or an explicit when-not-to-use case.

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