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

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

The description discloses what is returned (ID, description, disk size, price, location) and implies a read operation. However, the annotations set readOnlyHint=false, which is unusual for a list operation, and the description does not explain this or add caveats like pagination or freshness. The added fields are useful, but more context could be 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?

The description is two sentences with no redundant words. It states the purpose, lists output fields, and gives usage guidance efficiently. Every sentence earns its place.

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 tool with no parameters and no output schema, the description is largely complete: it names the returned fields and explicitly ties usage to create_container_registry. It could mention response format or that results should be fetched fresh, but these are minor given the 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?

There are zero parameters, so the description is not required to explain parameter details. It still adds value by listing the return fields, which is the semantic core of the tool. Baseline for zero parameters is 4.

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 clearly identifies the resource: available tariffs for Container Registry, including ID, description, disk size, price, and location. This distinguishes it from related tools like list_container_registries and other preset-listing tools.

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 guidance: 'Используй перед create_container_registry, чтобы выбрать preset_id' (use before create_container_registry to choose preset_id). This clearly tells the agent when to call it, though it does not mention when not to use it or alternatives.

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