Создание выделенного сервера

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

Annotations already indicate a write operation (readOnlyHint=false). The description confirms creation and points out required/optional fields but does not add significant behavioral details such as billing implications, creation duration, or return value. The prerequisite for preset_id is useful but also present in the schema.

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 compact and well-structured: one sentence for purpose, one for required fields, and one for optional fields and prerequisite. Every sentence conveys necessary 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 create tool with 11 parameters and no output schema, the description covers core usage: purpose, required fields, major optional fields, and the critical prerequisite. Minor omissions (e.g., comment, bandwidth_id) are covered by the schema, but the description is sufficiently complete for practical invocation.

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 parameters are already well-documented. The description provides a high-level summary of optional fields (OS, panel, additional services) but largely restates schema info. It adds value by grouping fields into required and optional, but does not compensate beyond that.

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 the action: 'Создаёт новый выделенный (dedicated) физический сервер' (creates a new dedicated physical server). It distinguishes from regular server creation by specifying 'dedicated physical' and is clearly differentiated from sibling tools like create_server and create_timeweb_app.

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 prerequisite: 'Перед вызовом получи preset_id через list_dedicated_server_presets' (obtain preset_id beforehand). Clearly lists required fields and indicates optional categories. Does not explicitly state when not to use, but context makes it clear this tool is for dedicated servers only.

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