Изменение конфигурации дополнения

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

Annotations already indicate that the tool is not read-only, not destructive, and not idempotent. The description adds minimal behavioral context beyond stating that it changes configuration and version, which is already implied by the name and title. No additional side effects or prerequisites are disclosed.

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 concise (two sentences) and front-loaded with the purpose. However, the second sentence, 'Нужны type, config_type, yaml_config, version', is redundant with the schema and incomplete, as it omits two required parameters. This slightly misleads and reduces clarity.

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?

The description covers the tool's core action and mentions previously installed addons, but it lacks information about return values (no output schema) and provides an incomplete parameter list. Given the tool's complexity (6 required parameters), the description is not fully complete.

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 100%, with all six parameters having detailed descriptions. The description lists only four of the six required parameters (type, config_type, yaml_config, version), omitting cluster_id and addon_id. It adds no extra semantic value beyond what the schema already provides.

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 tool's purpose: 'Изменяет конфигурацию или версию ранее установленного дополнения' (changes configuration or version of a previously installed addon). This is a specific verb+resource pair and distinguishes it from install/uninstall by noting the addon must be previously installed.

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 phrase 'ранее установленного дополнения' implies usage for existing addons, providing clear context for when this tool should be used. However, it does not explicitly mention alternatives or exclusions, such as 'use install_k8s_addon for new addons'.

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