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, so safety is largely covered. The description adds genuine value by stating it 'opens nothing by itself' and returns procedural steps rather than data, but it doesn't describe the shape of the returned steps or any caveats about the browser follow-up.

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 behavior is front-loaded, but the definition is dense and runs long, including an API inventory ('four developer APIs, Widget, Webhooks, Chat and Bot') and a dated verification note ('checked 20 Oct 2026'). That detail justifies the browser path but costs more space than the selection decision requires.

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 covers the essentials: what is returned (step-by-step screens/buttons/fields), what the tool does not do, and which tools perform the actual action. It could mention that report specifics (date range, metrics) must be supplied when driving the browser, but overall it is sufficient.

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 parameter-related for the description to compensate for. No misleading parameter language is present.

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 says the tool returns step-by-step instructions for producing an aggregated report in JivoChat, distinct from the sibling cotlet_app_guide and the jivochat_list_* data tools. The name suggests it fetches a report, but the body corrects that within one sentence, so an agent can identify the real purpose.

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 explicitly hands off: call this first, then act with the cotlet_browser_* tools against the user's JivoChat Cloud Browser. It also explains why the browser route is required (no REST API for chats/clients/history), which is useful context. It stops short of naming other guide-type siblings as alternatives.

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