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

The annotations already declare readOnlyHint, openWorldHint=false, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description usefully adds that nothing is opened or mutated and that the payload is procedural guidance rather than account data, which goes beyond the annotations, but it says nothing about how that guidance is scoped or presented in the response.

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 core (returns step-by-step instructions; nothing is opened; continue with cotlet_browser_*) is front-loaded and clear, but the closing sentence about Gladly's REST API and the absence of an official MCP server, complete with a 'checked 20 Oct 2026' timestamp, is tangential justification that does not help the agent decide or invoke.

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, no output schema and full annotation coverage, the definition gives what an agent needs: what comes back (screens, buttons, fields), that no external action occurs, and which tools carry out the actual work. It is nearly complete for a simple no-arg guidance tool; only the ambiguity between 'list' and 'explains how to list' keeps it from a 5.

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 the baseline is 4 and there is nothing the description could add. It correctly avoids inventing argument behavior for a no-argument call.

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 name and title say 'List conversations', but the description says the tool returns step-by-step instructions for how to list them and 'opens nothing by itself'. That second framing is the accurate one and is stated explicitly, but the mismatch between the verb in the name and the actual delivery (a guide, not data) leaves the agent reconciling two readings of what the call produces.

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 routes the agent explicitly: call this to get the how-to, then execute with the cotlet_browser_* tools in the user's Gladly Cloud Browser, and it states clearly that this tool performs no action itself. There is no when-not guidance or mention of when a different Gladly tool would be preferred, so it stops short of a 5.

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