Список доменов

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it returns all domains and mentions the HTTP endpoint, but it does not disclose pagination behavior, authentication requirements, rate limits, response format, or any caveats. For a read-only list operation, this is minimal transparency.

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 very concise: two short fragments in Russian and the HTTP endpoint. Every word contributes to the purpose. It is front-loaded and easily parseable, with no wasted text.

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?

The tool is simple (no params, no output schema), but the description does not explain what the response looks like or any nuances of the list operation. Given that there is no output schema, the description should provide more detail about return values or potential limitations. While it is adequate for a basic list, it leaves some gaps.

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 zero parameters, and the schema is empty with 100% coverage. The description adds no parameter information, but this is acceptable because there are no parameters to describe. Per the baseline for 0 params, a score of 4 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 'Все домены аккаунта' (all domains of the account), which clearly indicates the resource (domains) and the action (listing all). The HTTP method 'GET /api/v1/domains' reinforces the retrieval intent. This distinguishes it from siblings like get_domain (single domain) and list_dns_records (a different resource).

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 implicitly conveys that this is for listing all domains, but it does not explicitly state when to use this tool instead of alternatives such as get_domain. There is no exclusion guidance or mention of when not to use it. The context is clear from the resource name, but no explicit guidance is provided.

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