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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description is consistent with them by stating it 'opens nothing by itself'. Beyond that it discloses the return content (step-by-step screens, buttons, fields) and the follow-up mechanism (cotlet_browser_*), which the annotations do not convey. It does not say whether the user must be logged in or whether a browser session must be pre-opened.

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 and the follow-up tools are named early, but 'from ChatGPT, Claude or any AI agent' is filler marketing, and the closing aside about Kommo's official REST API and a dated documentation check is tangential to calling the tool. The stream-of-consciousness punctuation (semicolon, 'then do it with') makes it slower to parse than necessary.

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 must explain what comes back, and it does (step-by-step instructions rather than a created task). However, it leaves operational preconditions unstated — whether a Kommo browser session must be open, or what happens if the user is not logged in — which matters for a guidance-plus-automation flow.

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 and the schema is closed (additionalProperties: false), so there is nothing for the description to disambiguate. Baseline applies; no parameter detail is needed.

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 opening clause 'Create task in the user's own Kommo account' reads as if the tool performs the creation, but the next clause reverses that: it 'returns how to do it in Kommo step by step' and 'opens nothing by itself'. The agent must parse the whole sentence to learn the tool is really a guidance generator; the true verb+resource (return instructions for creating a Kommo task) is buried. It does at least route to the cotlet_browser_* siblings for actual execution.

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?

Explicit sequencing is given: call this to get screens/buttons/fields, then perform the action with the cotlet_browser_* tools in the user's Kommo Cloud Browser. That names the alternative workflow and the handoff condition. No explicit 'when not to use' case is stated, keeping it just 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.