Создание группы нод

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

The description adds the mutual exclusivity constraint, which is not visible from annotations. Annotations already indicate this is a mutating operation (readOnlyHint false), so the description does not need to restate that. It lacks details on side effects or return values, but annotations provide the basic behavioral profile.

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 two concise sentences, front-loaded with the primary action and required parameters. Every word earns its place, with no redundant fluff.

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 10 parameters and a nested configuration object, the description covers the critical decision points (required fields, tariff selection). The schema descriptions cover the remaining parameters, so the description is sufficiently complete for an agent to select and invoke the tool correctly.

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 100%, so all parameters already have descriptions. The description adds value by clarifying the mutually exclusive relationship between preset_id and configuration, which is not stated in the schema. It also reiterates required fields, reinforcing what is already present.

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 creates a new worker node group in a cluster, using a specific verb and resource. It distinguishes itself from sibling tools like delete_k8s_node_group or increase_k8s_node_group_nodes by focusing on the creation action.

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 description gives clear usage context by specifying required fields (name, node_count) and the mutually exclusive choice between preset_id and configuration. It does not explicitly mention alternatives or when-not-to-use, but the creation context is unambiguous.

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