Список реестров контейнеров

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

The description describes a read-only list operation, but annotations declare readOnlyHint=false, creating a direct contradiction. According to rules, this must be scored 1 and flagged as 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?

The description is two sentences, each serving a clear purpose: the first defines the result set, the second gives a usage directive. No unnecessary 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?

Given the tool has no parameters and no output schema, the description provides all essential information: what it returns (with field list) and when to use it. It is sufficient for an agent to select and invoke the tool correctly.

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, so the schema provides no parameter information. The baseline for 0 params is 4, and the description additionally clarifies the output fields, so it adds value without needing parameter details.

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 explicitly states 'Возвращает список всех реестров контейнеров' (returns a list of all container registries) and enumerates the returned fields, making it clear this is a list operation. It distinguishes itself from sibling tools like list_container_registry_repositories and list_container_registry_presets by focusing on the top-level registry objects.

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 second sentence instructs to use it before registry operations to obtain the registry ID, giving clear when-to-use guidance. However, it doesn't explicitly mention alternatives or exclusions, so not a perfect 5.

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