Список доменных зон (TLD)

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

The description states 'Возвращает список' (returns a list), clearly indicating a read-only operation. However, annotations set readOnlyHint to false, which suggests the tool may modify state. This is a direct contradiction between the description and annotations, so the score is 1.

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. The first sentence states the exact purpose (list TLDs with prices), and the second provides a clear usage directive. No unnecessary words or repetition.

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 parameterless list operation with no output schema, the description covers the essential context: what is returned, what information is included, and when to use it. It is fully adequate for the tool's simplicity.

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 tool has 0 parameters and the schema is empty, so schema coverage is trivially 100%. With no parameters to document, the description does not need to add parameter information, and the baseline 4 applies.

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 uses a specific verb 'Возвращает список' (returns a list) and identifies the resource as 'всех доступных доменных зон' (all available domain zones), including registration and renewal prices. This clearly distinguishes it from sibling get_tld, which returns a single TLD.

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 provides explicit usage context: 'Используй перед созданием заявки на регистрацию' (Use before creating a registration request). It does not mention alternatives or exclusions, so it earns a 4 rather than a 5.

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