Update catalog custom fields

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

The description adds no behavioral context beyond what the annotations already declare (openWorldHint, idempotentHint). It does not disclose whether updates replace or merge existing fields, side effects, permission requirements, or what happens on partial failure, leaving the agent to guess.

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 with no redundant wording, making it highly concise and easy to parse. However, it is so terse that it borders on under-specification, similar to 'Process'.

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?

This mutation tool lacks an output schema and provides minimal description. The critical behavior is undefined: whether the update is additive, replaces the entire field set, or only touches specified fields. Given the existence of update_one, the incomplete explanation is particularly problematic for correct agent selection.

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 coverage is 0% and the description does not compensate. The 'fields' parameter is an array of arbitrary objects with propertyNames but no semantics—what keys are allowed, how to identify existing fields, or the expected format. 'catalog_id' is only implied by the name, not explained.

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 identifies the resource (catalog custom fields) and action (update), but it is essentially a restatement of the title with no additional specifics. It does not distinguish itself from the sibling tool kommo_catalog_custom_fields_update_one, nor does it clarify whether this is a batch operation or what 'update' entails beyond a generic verb.

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 guidance is provided on when to use this tool versus alternatives. With many update-related siblings (update_one, update for other entities), there is no mention of batch vs. single-field scope, or any exclusions or prerequisites.

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