DNS-записи домена по умолчанию

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

Annotation readOnlyHint=false contradicts the description's clear read-only intent ('Возвращает список' - returns a list). This is a serious inconsistency. Additionally, no behavioral details beyond the contradiction are provided.

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?

Single, well-structured sentence that front-loads the action and resource. No wasted words.

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?

While the tool is simple, the description omits any details about the return value structure (since no output schema), and the annotation contradiction undermines trust. It also lacks explicit comparison to list_dns_records, which is directly relevant.

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 already provides 100% coverage for the sole parameter fqdn. The description adds that the tool works for domains OR subdomains, which is extra context beyond the schema's 'полное имя домена'.

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 uses specific verb 'Возвращает список' (returns a list) and identifies the resource as default DNS records for a domain or subdomain, clearly distinguishing from the sibling tool 'list_dns_records'. It is precise and unambiguous.

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?

Mentions that these are Timeweb system records, implying use for default/system records rather than user-defined ones. However, it doesn't explicitly contrast with list_dns_records or state when not to use this tool, so it lacks explicit exclusions.

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