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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, but the description adds real context beyond them: the output is procedural (screens, buttons, fields), the tool performs no actions itself, and execution requires the Chatwoot Cloud Browser via cotlet_browser_* tools. It still does not state whether a connected Chatwoot workspace or authentication is a precondition.

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 behavioral explanation is front-loaded and useful, but the closing sentence about Chatwoot's REST API, Application API, CLI client and lack of an official MCP server does little to help an agent select or invoke this tool. That sentence inflates length without improving decision-making.

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, no-output-schema tool the description covers the essentials: what comes back (procedural steps) and what to do next. The gaps are meaningful though — it never says whether the Chatwoot workspace must already be connected, or what to do if the returned steps reference screens the agent cannot navigate.

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 semantics to explain and the baseline applies. The description correctly implies no input is required beyond implicitly targeting the user's own account.

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 verb and resource ("List conversations in the user's own Chatwoot account") and then immediately corrects expectations by stating the tool returns step-by-step instructions rather than data. That correction is what separates it from the action siblings (chatwoot_reply_to_conversation, chatwoot_add_labels), though it never names any sibling directly.

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 gives a usable sequence: this tool yields the steps, "then do it with the cotlet_browser_* tools." It also clarifies the tool "opens nothing by itself." However, there is no guidance on when to prefer this over cotlet_app_guide, nor any exclusion relative to the chatwoot_* action tools that share the same domain.

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