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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false. Beyond those, the description adds a genuinely material trait: the tool returns procedural guidance (screens, buttons, fields) and performs no action itself, requiring a follow-up browser step. That is exactly the kind of context annotations cannot express. It does not describe the shape of the returned guidance or whether a Cloud Browser session must already exist.

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 front-loaded sentence states purpose and audience, then the operative behavior and the follow-up requirement. The closing note about Freshchat's REST API and lack of an official MCP server is contextual but somewhat tangential, adding length without changing invocation.

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 must carry most of the burden, and it does explain the return type loosely. But an agent still lacks concrete detail on what the returned steps look like and any precondition about an open Cloud Browser session, leaving a gap for a tool whose entire value is the returned instructions.

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 convey and the baseline of 4 applies. Nothing in the description conflicts with the empty schema.

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 states the specific resource (a Freshchat conversation) and, crucially, clarifies the actual output: step-by-step instructions for performing the read in Freshchat rather than the conversation data itself. That resolves the tension between the name 'read_conversation' and the real behavior. It stops short of naming sibling tools (e.g., freshchat_list_conversations, cotlet_browser_read) that an agent might otherwise pick.

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?

There is useful sequencing guidance: the tool 'opens nothing by itself; then do it with the cotlet_browser_* tools.' That tells the agent this is a preparatory/build-a-plan call. However, it gives no when-not guidance and does not distinguish this from the other freshchat_* API tools or cotlet_browser_read, so selection against alternatives is left to inference.

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