List website chat buttons

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe read-only nature is disclosed by structured data. The description adds no extra behavioral context such as pagination behavior, output details, or scope limitations, but it does not contradict the annotations either.

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 a single concise sentence with the action and resource front-loaded. It contains no filler, though the phrase 'CRM plugins / website chat buttons' is slightly ambiguous in whether these are the same or separate categories.

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?

Given the simple read-only nature, optional pagination parameters, and absence of an output schema, the description is minimally adequate but not complete. It lacks guidance on pagination, the relationship to get/create/update plugin tools, and what exactly constitutes a 'website chat button.'

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 input schema defines page and limit with types and constraints but contains no descriptions, so schema description coverage is 0%. The description does not clarify these parameters or how pagination works, leaving the agent to rely solely on the parameter names.

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 specific verb 'List' and identifies the resource as 'CRM plugins / website chat buttons,' clearly matching the title. It distinguishes the operation as listing, though it does not explicitly differentiate from closely related tools like kommo_crm_plugins_get or kommo_widgets_list.

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?

The description provides no guidance on when to use this tool versus alternatives. Sibling tools such as kommo_crm_plugins_get, kommo_crm_plugins_create, and kommo_widgets_list exist, but the description gives no hints about choosing this list tool over them.

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