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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds value by mentioning bulk support and filterability. However, it does not disclose return format, pagination behavior, or how catalog_id and catalog_ids interact, which would be useful beyond the annotations.

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 brief and avoids unnecessary words, fitting within a few lines. However, the action line ('action: list | elements') adds confusion rather than clarity, slightly reducing structure quality.

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 7 parameters, no output schema, and 0% parameter documentation, the description is insufficient. It does not explain how to use the tool effectively, what the response looks like, or how to combine parameters. The bulk support is mentioned but not detailed.

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%, so the description must compensate. It hints at filtering/searching ('filtrável/buscável') and bulk via catalog_ids, but it does not explain parameters like page, limit, query, filter, account, or catalog_id. The mapping between parameters and their usage is largely absent.

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 states it deals with catalogs and elements, listing both 'list' and 'elements' actions, but it's unclear which action this specific tool performs. The name suggests 'elements', and it mentions '[Flattened action: elements]', but the description still includes 'list' without clearly distinguishing from the sibling kommo_catalogs_list. This ambiguity reduces clarity about the tool's exact 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?

The description mentions bulk support with catalog_ids and filtering, but it does not explicitly state when to use this tool versus kommo_catalogs_list or other siblings. There is no clear 'use this for elements, use that for catalogs' guidance, leaving the agent to infer context.

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