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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true; the description reinforces this by stating it 'opens nothing by itself', which directly answers the main risk an agent might worry about for a merge operation. It also characterizes the return content (screens, buttons, fields). It does not describe the exact response shape or length, leaving a small gap.

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 key point (returns steps, does nothing itself, then use browser tools) is front-loaded, which is good. The trailing sentence about FreeScout's paid API module and the dated 'checked 23 Oct 2026' note is justification padding that does not help an agent invoke the tool more correctly.

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, no output schema, and safety fully covered by annotations, the description supplies what is missing: that the tool returns procedural guidance and that execution happens through browser tools. Nothing essential to correct invocation is absent.

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 (empty object schema), so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no arguments are needed.

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 makes clear this is a guidance tool, not an actor: it 'Returns how to do it in FreeScout step by step (screens, buttons, fields) and opens nothing by itself.' This disambiguates the potentially misleading name/title 'Merge conversations', which alone would suggest it performs the merge. It does not, however, contrast itself directly with sibling FreeScout tools such as freescout_move_conversation.

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 an explicit follow-on path: read the steps here, then execute them with the cotlet_browser_* tools in the user's FreeScout Cloud Browser, and it explains why (no official MCP server, API gated behind a paid module). It stops short of stating when NOT to reach for this versus other siblings, but the intended usage sequence is unambiguous.

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