kommo_list_catalog_elements

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

No annotations are provided, and the description only states 'List...', which implicitly suggests a read-only operation. However, it does not explicitly disclose behavioral traits such as pagination, rate limits, or that it only reads data. More detail is needed for a mutation-free guarantee.

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 short sentence, which is concise but omits important details. While not verbose, it fails to provide sufficient context for effective tool use.

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 lack of output schema, zero parameter descriptions, and no behavioral annotations, the description is severely incomplete. It does not inform the agent about the return format, pagination behavior, or any other operational details necessary for correct invocation.

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 has 3 parameters with 0% description coverage, and the tool description provides no additional context about what 'catalog_id', 'page', or 'limit' mean or how they affect the output. This leaves the agent without crucial information for parameter selection.

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 explicitly states 'List elements (products) within a catalog', clearly identifying the action (list), resource (elements/products), and scope (within a catalog). It distinguishes from sibling tools like kommo_list_catalogs which list catalogs themselves, and other list tools for different entities.

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 implies usage when needing to view products in a catalog, but provides no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The context is clear but lacks directiveness.

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