Deletes a specific queue version by ID when confirmation is provided, removing outdated or unwanted queue configurations from Yandex Tracker.
Delete a queue version by id.
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | No | Set to true to confirm this destructive/bulk operation | |
| versionId | Yes |
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered structurally. The description adds nothing beyond the verb 'Delete' - it does not mention the confirm requirement, irreversibility, or any effect on dependent entities, so it earns no extra behavioral credit.
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?
A single efficient sentence with the resource and selector front-loaded and no filler. It is well-formed, though the brevity borders on under-specification for a destructive tool.
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 destructive mutation with no output schema, the description omits the confirm=true requirement, irreversibility, and consequences. Annotations cover the safety profile, but the description leaves the agent without the operational context needed to invoke it 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?
Schema description coverage is 50%: 'confirm' is documented in the schema but 'versionId' is bare. 'By id' in the description slightly compensates by implying versionId is the queue version identifier, but the description ignores the confirm flag entirely. Marginal value over the schema.
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?
States a specific verb ('Delete') and resource ('queue version'), with 'by id' indicating the selector. This clearly distinguishes it from the sibling read/update/create operations (get_queue_version, update_queue_version, create_queue_version), though it does not explicitly name alternatives.
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?
No guidance on when to use this versus alternatives, no prerequisites, and no warning that the operation is irreversible. The agent gets no context about the conditions under which deletion is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.