Create catalogs

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

The description adds no behavioral context beyond the bare action. The openWorldHint annotation indicates schema flexibility, but the description does not mention any side effects, permissions, required auth, or success/failure behavior. There is no contradiction, but also no added value beyond the annotation.

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, front-loaded, and concise sentence with no wasted words. It immediately conveys the action and resource, making it easy for an agent to parse.

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 tool has a simple schema but no output schema and low schema coverage, the description is too sparse. It does not explain how to construct a valid catalog object, what fields are expected, or what the API returns on success or failure. This is inadequate for reliable 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?

Schema description coverage is 0%, so the description must compensate. The phrase 'one or more catalogs' correctly implies that the 'catalogs' parameter is an array, but it provides no details about the structure of each catalog object, required fields, or example values. This leaves significant ambiguity for an open-ended schema.

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 clearly states the verb 'Create' and the resource 'catalogs', which is specific and distinguishes it from sibling tools like kommo_catalogs_list, kommo_catalogs_get, and kommo_catalogs_update. There is no ambiguity about what the tool does.

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?

Usage is implied by the verb 'create' (e.g., for adding new catalogs, not modifying existing ones), but the description lacks explicit guidance on when to prefer this tool over alternatives like update or delete. No prerequisites or exclusions are mentioned.

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