Создание сервера

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

Annotations already indicate non-read-only, non-destructive behavior. The description adds the XOR constraints, but these are already present in the schema's parameter descriptions. No additional behavioral details such as rate limits, idempotency, or side effects are disclosed beyond what annotations and schema provide.

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?

Two sentences, front-loaded with the core action ('Creates a new cloud server'), followed by a compact enumeration of modes and supported parameters. Every phrase provides information without redundancy.

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?

For a 19-parameter tool with 100% schema coverage and no output schema, the description gives a concise overview and emphasizes the key constraints (mode choices, OS choice). It omits some optional parameters (comment, software_id), but those are documented in the schema. The lack of return-value information is acceptable given the absence of an output schema.

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 the schema fully documents each parameter. The description summarizes groups (e.g., cpu/ram/disk for configurator mode) and repeats the XOR constraints already in the schema. It adds no new semantic meaning beyond the 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?

Description clearly states 'Creates a new cloud server', a specific verb+resource. It distinguishes from sibling tools like create_dedicated_server and create_k8s_cluster by explicitly mentioning 'cloud' and detailing creation modes (preset/configurator) and OS selection.

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?

Provides explicit usage guidance for parameter selection: 'preset_id XOR configurator_id' and 'os_id XOR image_id', clarifying when to use which parameters. It does not explicitly name alternative tools for exclusion, but the context of creating a new cloud server is clear from the description and name.

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