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

Annotations already declare readOnlyHint and destructiveHint=false, and the description reinforces this with 'opens nothing by itself', which is consistent rather than contradictory. Beyond the annotations it discloses the actual return shape (screens, buttons, fields) and the execution dependency on browser tools. The background paragraph about JivoChat's four APIs and the absence of an official MCP server adds context, though the 'checked 20 Oct 2026' date is a future timestamp that slightly undermines credibility.

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 operative content is front-loaded in the first two sentences, which is good. The third sentence about Widget, Webhooks, Chat and Bot APIs exists to justify the tool's existence rather than to help an agent invoke it, and it dilutes an otherwise tight definition.

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 parameterless guide tool with no output schema, the description covers what comes back (step-by-step screens, buttons, fields), confirms no side effects, and names the next tool family to use. An agent has enough to call it and act on the result. Only the relationship to cotlet_app_guide is left unstated.

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. Nothing in the description is needed to disambiguate inputs, and it does not waste space inventing parameter commentary that the empty schema already settles.

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 first sentence names a specific verb and resource (list clients in the user's own JivoChat account), and the second clarifies that the tool returns step-by-step instructions rather than data. That clarification is essential because it contradicts the natural reading of the name 'list_clients', so the description earns credit for resolving it. It stops short of 5 because it never differentiates itself from the sibling cotlet_app_guide, which appears to serve the same instruction role.

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 follow-on path: this tool returns guidance, then the agent executes with cotlet_browser_* in the JivoChat Cloud Browser. That is genuine workflow guidance. However, it states no condition for choosing this over jivochat_list_chats or jivochat_merge_clients, and no prerequisites or exclusions are named.

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