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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world. The description adds the genuinely important behavioral fact that it 'opens nothing by itself' and only returns procedural guidance, plus the note that Freshchat has a v2 REST API but no official MCP server. That is real context beyond the annotations, though it omits what happens if the guidance leads to a dead end.

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?

Front-loaded with the key point that it returns guidance rather than data, and the sentences are short. The 'from ChatGPT, Claude or any AI agent' clause and the dated API-check note are marginally useful filler rather than essential information.

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 no output schema, the definition covers what is returned (screens, buttons, fields), that nothing is executed, and which tools to use next. It could say more about outcome when the user's plan or permissions don't expose CSAT, but the essentials are present.

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?

There are zero parameters, so the baseline is 4. The description correctly implies no input is required, consistent 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 a specific resource (CSAT report in Freshchat) and, crucially, clarifies that the tool returns step-by-step instructions rather than fetching data itself, which corrects a misleading name. It also distinguishes itself from the cotlet_browser_* family. It is slightly muddled by the marketing phrase about ChatGPT/Claude/agents, but the core purpose is unambiguous.

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 clear two-step workflow: call this to get guidance, then execute with cotlet_browser_* in the Freshchat Cloud Browser. What's missing is any explicit statement of when NOT to use it (e.g., when an API-backed CSAT endpoint exists) or what it returns when the user lacks a Freshchat account.

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