Update single catalog element

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

The annotations include idempotentHint and openWorldHint, but the description adds no extra behavioral context beyond stating the operation. It does not explain whether updates are partial, what fields are affected, or any side effects, leaving the agent reliant on assumptions.

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 sentence with no redundant words, making it front-loaded and technically concise. However, this brevity comes at the cost of omitting critical details, so it is not appropriately sized for the tool's complexity.

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 nested 'element' parameter, lack of an output schema, and a large set of sibling tools, this one-line description is severely incomplete. It provides insufficient context for an agent to safely invoke the tool without additional documentation.

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 schema description coverage is 0%, and the description provides no explanation of the 'element' object parameter, which is a complex nested object. The only parameter mentioned is 'ID', leaving the agent with no understanding of how to structure the update payload.

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 action (update), resource (catalog element), and scope (single element by ID). This distinguishes it from list/get/create operations, though it does not explicitly differentiate it from the sibling 'update' tool.

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 like kommo_catalog_elements_update or create. There are no exclusions, prerequisites, or context for selecting this tool.

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