Удаление реестра контейнеров

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

The description explicitly states that deletion is irreversible and all images will be lost, which is destructive behavior. However, the annotation destructiveHint is false, directly contradicting this. This is a serious inconsistency that would mislead an agent about the tool's safety profile.

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, front-loaded with the key action, and includes a concise warning. Every sentence contributes meaningful information without redundancy or unnecessary verbosity.

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 description covers the essential destructive behavior and user warning, which is sufficient for a simple single-parameter delete operation. However, the contradiction with destructiveHint creates confusion and undermines the overall contextual completeness, as the agent cannot rely on the annotations.

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 schema description covers the single parameter (registry_id) completely with a required-field note and explanation. The tool description does not add any additional parameter semantics beyond what the schema already provides, so the baseline score of 3 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 clearly states the tool deletes a container registry irreversibly. The verb 'Удаляет' (deletes) and resource 'реестр контейнеров' (container registry) are specific, and it distinguishes itself from sibling tools like create/update/get/list container registries.

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 context on when to use the tool (to permanently delete a registry) and includes a warning to ensure the registry is not in use before deletion. It does not explicitly list alternatives or when-not-to-use scenarios, but the context is clear enough.

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