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

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

Description claims read-only behavior ('Возвращает список' - returns a list), but annotations set readOnlyHint=false and idempotentHint=false, contradicting the described behavior. No additional behavioral details like pagination or rate limits are provided. This is an annotation contradiction.

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?

Two concise sentences, first describes function, second gives usage guidance. No redundant content.

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 zero-parameter list tool, the description covers return fields and usage context. However, the annotation contradiction and lack of pagination/sorting details leave gaps; no output schema means the agent relies on the incomplete list of 'key parameters'.

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?

Tool has zero parameters; schema coverage is 100% (trivially). Description adds no parameter info needed, so 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?

Description clearly states it returns a list of all account domains with specific fields (ID, FQDN, status, expiry, auto-renewal), using the specific verb 'Возвращает' (returns). This distinguishes it from siblings like get_domain, add_domain, or check_domain.

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 usage context: 'Используй перед любой операцией над доменом' (Use before any domain operation), indicating when to call. However, it doesn't mention exclusions or alternative tools, so not a 5.

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