Добавление домена на аккаунт

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

Annotations already convey readOnly=false and destructive=false. The description adds the behavioral nuance that the tool does not register a new domain, only adds existing ones. However, it does not describe side effects like whether existing DNS records are imported, whether adding an already-managed domain fails, or any authorization requirements. Some additional behavioral context is provided but not extensive.

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 sentences: the first states the action and purpose, the second provides an exclusion and points to the alternative. It is front-loaded, concise, and every sentence earns its place.

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 simple single-parameter tool with no output schema, the description covers the core purpose, the prerequisite (domain already registered elsewhere), and the key distinction from create_domain_request. It lacks explicit mention of response behavior or post-conditions, but these are not critical for this simple mutation tool given the annotations.

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 has 100% description coverage, and the parameter 'fqdn' is well described as a full domain name already registered elsewhere. The tool description reinforces this by mentioning 'already registered in another place,' but does not add additional parameter-level detail beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific action: 'adds an already registered elsewhere domain to the Timeweb Cloud account for DNS and name-server management.' It clearly distinguishes from registration by explicitly saying 'Does not perform registration,' which differentiates it from the sibling create_domain_request.

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 explicitly states when not to use the tool: 'Does not perform registration — for registration use create_domain_request.' This names the alternative and provides a clear conditional. It also implies use when the domain is already registered elsewhere, which is helpful guidance.

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