Add website chat button

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

Annotations include openWorldHint=true, but the description adds no behavioral context beyond that. It does not disclose what the free-form body requires, what happens after creation, or any side effects. For a tool that creates a plugin/chat button, expectations about required fields or external effects are entirely absent.

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 description is extremely short, essentially restating the title. It is under-specified rather than concise, providing no structured breakdown of inputs or outcomes. The slash creates ambiguity without clarifying the resource.

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 a free-form body parameter, no output schema, and openWorldHint, the description should provide examples or field expectations. It does not. The tool is likely unusable without external knowledge of the Kommo CRM API.

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?

Schema description coverage is 0%, and the schema only defines a generic 'body' object with no property constraints. The description does not explain what the body should contain (e.g., plugin name, chat widget settings). The single parameter is semantically opaque.

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 uses the verb 'Create' with resource 'CRM plugin / website chat button', which clearly identifies a create operation distinct from sibling tools like list, get, update, and connect_chat. The slight ambiguity of the slash between 'CRM plugin' and 'website chat button' prevents a 5.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that listing, retrieving, updating, or connecting chat are handled by other tools, nor does it explain prerequisites or typical scenarios. The description is purely a definition, not usage guidance.

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