Create catalog elements

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

The only annotation is openWorldHint=true, which gives no safety or read/write clues. The description adds no information about batch size limits, required element structure, return values, or side effects, so the agent lacks transparency for a mutating operation.

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 one short sentence—'Add elements to a catalog.'—which is concise and front-loaded. However, it's too terse to convey usage or parameter details, but that's not necessarily a conciseness failure; every word earns its place.

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?

For a create operation with two required parameters (catalog_id, elements) and no output schema, the description is insufficient. It does not specify how elements are structured, whether the catalog must already exist, or what a successful response looks like, leaving the agent with significant gaps.

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% (no parameter descriptions). The description does not explain catalog_id or the elements array, nor does it mention the requirement that elements must have at least one item. It is effectively a restatement of the tool's name.

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 'Add elements to a catalog' clearly names the verb (add) and resource (elements to a catalog), distinguishing it from sibling tools like kommo_catalog_elements_list/get/update. The tool name corroborates this, making its purpose unambiguous.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives such as kommo_catalogs_create or kommo_catalog_elements_update, and there are no prerequisites or context clues. An agent would have to infer from the name alone.

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