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, and the description is fully consistent with them ('opens nothing by itself'). It adds genuinely non-derivable context: the response is a step-by-step guide with screens, buttons and fields, and the real mutation happens through separate browser tools. The note about Kommo's REST API lacking a hosted MCP server explains why the browser path is required, which is useful scoping information.

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?

Three sentences, each carrying distinct information: what is returned, how to act on it, and why browser tools rather than an API. It is dense and slightly awkward mid-sentence ('...step by step (screens, buttons, fields) and opens nothing by itself; then...'), but nothing is padding and the key constraint is surfaced early.

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?

There is no output schema and no parameters, so the description must carry the whole contract, and it does: the return shape (ordered steps with screens, buttons, fields), the non-execution guarantee, the follow-up tool family, and the rationale for the browser route. An agent has everything needed to call it correctly and chain it into cotlet_browser_*.

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?

With zero parameters and 100% schema description coverage, there is no parameter semantics to explain, so the baseline applies. The description correctly avoids inventing inputs that do not exist.

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 names a specific verb and resource (reply to chat in Kommo) and immediately corrects the most likely misreading by stating it 'returns how to do it in Kommo step by step' and 'opens nothing by itself.' That resolves the name-versus-behavior tension, though an agent skimming only the name would still expect an action tool. It also distinguishes itself from the cotlet_browser_* siblings by assigning them the actual execution 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 an explicit two-step workflow: call this to get instructions, then perform the steps with cotlet_browser_* in the user's Kommo Cloud Browser. What is missing is a negative case — when not to use this (e.g., versus kommo_add_note for non-chat actions) — so the routing is clear but not exhaustive.

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